apolo-cad

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

79/79 tools missing one or more hints — get_scene (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_command_schemas (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +76 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

7 tools describe read intent but their handlers mutate — export_flat_pattern (line 713: target.write_bytes(data)); drop_test (line 731: target.write_bytes(gif)); gravity_test (line 920: target.write_bytes(gif))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

61/79 tool handlers declare input schemas (77%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/79 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

52/79 tools referenced in tests (66%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 child_process/subprocess calls in production code — runs shell commands (core/apolo/agent/script_wrapper.py:36, core/apolo/library/loader.py:28)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Tool description accuracy

7 tools have description/behavior mismatches: export_flat_pattern: description implies read-only but handler writes/deletes/executes; drop_test: description implies read-only but handler writes/deletes/executes; gravity_test: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.