jama-connect

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

70/70 tools missing one or more hints — jama_list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jama_get_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jama_get_item (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +67 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.

Tool inputs are validated

62/70 tool handlers declare input schemas (89%)

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

Tool handlers catch errors

Only 1/70 tool handlers wrap calls in try/catch (1%)

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

Tool test coverage

Only 0/70 tools referenced in tests (0%)

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

Shell command execution

11 child_process calls — runs shell commands

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

Readable source code

18 files appear obfuscated

Ship unminified, readable source.