Laver

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

30/30 tools missing one or more hints — list_workspaces (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_boards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_board (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +27 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

1 tool describes read intent but its handler mutates — get_ticket_attachment (line 669: mkdirSync(dirname(target), { recursive: true }))

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

Tool inputs are validated

23/30 tool handlers declare input schemas (77%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (LAVER_API_KEY_FILE → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Domain consistency

npm scope @laver doesn't match GitHub owner developyn

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

Tool description accuracy

get_ticket_attachment: description implies read-only but handler writes/deletes/executes

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