cas

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

35/35 tools missing one or more hints — list_directory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bulk_ingest_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ingest_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +32 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

1 tool perform destructive updates without destructiveHint — delete_edge deletes at line 924 (result = await v.graph_ops_service.unlink(edge_id, dry_run=dry_run))

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 inputs are validated

33/35 tool handlers declare input schemas (94%)

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

Tool handlers catch errors

34/35 tool handlers wrap calls in try/catch (97%)

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

Tool test coverage

Only 2/35 tools referenced in tests (6%)

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.