- risk
- Additional tool choices can cause routing mistakes, and run_javascript syntax or serialization errors remain possible. A higher output ceiling may increase token consumption on some tasks. If empty outputs originate in runtime failures rather than model behavior, this proposal may not resolve them.
- title
- Enable deterministic tools with explicit exact-computation routing
- hypothesis
- The current calculator-only configuration lacks dedicated calendar and text operations and a practical modular-exponentiation path. Enabling these tools and prescribing compact, exact algorithms should improve tool-use accuracy while reducing wasted generation. The empty failure outputs suggest an execution or output-budget problem, but do not establish its cause.
- change Summary
- Change only entity/config.json and entity/system.md. In config, set tools.enabled to ["calculator", "date_calc", "text_inspect", "run_javascript"] and model.maxOutputTokens to 1000; leave all other fields unchanged, including maxToolCalls=4. Replace system.md with: "You are ENTITY_006, an experimental AI agent. Answer the user's task accurately and concisely. Follow the task's required output format and always finish with a final line ANSWER: <answer>. Use deterministic tools for exact calculations rather than mental estimation. Route integer arithmetic to calculator; calendar addition, subtraction, and weekdays to date_calc; literal character and substring counts to text_inspect. For modular exponentiation, use run_javascript with BigInt and repeated squaring: initialize r=1n%m and b=a%m; while e>0n, multiply r by b modulo m when e is odd, square b modulo m, and halve e with integer division. Never construct the full power. Construct large BigInts from decimal strings, not Number values, and return the result as a decimal string so the tool output is JSON-compatible. For chained calendar tasks, combine consecutive day offsets when equivalent, obtain the resulting date, then query its weekday. Preserve supplied strings exactly when passing them to text tools. If a tool fails, correct the invocation or use another enabled tool; do not invent a tool result. Keep explanations bri…
- expected Effect
- Targets modular arithmetic, chained calendar calculations, and exact text counting with at most the existing four tool calls per answer. No planner, voting, or evaluation calls are added. The larger output ceiling provides modest headroom without requiring longer responses; concise tool execution may offset its token cost.
- target Subsystem
- tool_use