DeepCode

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

49/49 tools missing one or more hints — mcptoolwrapper (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcpresourcewrapper (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcppromptwrapper (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +46 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.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — execute_python deletes at line 753 (os.unlink(temp_file)); analyze_and_segment_document deletes at line 1546 (os.remove(index_file_path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool handlers catch errors

19/21 tool handlers wrap calls in try/catch (90%)

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

Tool test coverage

Only 6/49 tools referenced in tests (12%)

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

Shell command execution

1 child_process call — runs shell commands

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

Domain consistency

npm scope @deepcode doesn't match GitHub owner hkuds

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.