ForIT Microsoft Graph

Tool annotations

2/22 tools have annotations

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

All four hints declared on every tool

22/22 tools missing one or more hints — login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); logout (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify-login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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

9/15 tool handlers declare input schemas (60%)

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

Tool handlers catch errors

9/15 tool handlers wrap calls in try/catch (60%)

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

Tool test coverage

Only 2/22 tools referenced in tests (9%)

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 @example doesn't match GitHub owner foritllc

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