pwiz-ai

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

68/68 tools missing one or more hints — get_project_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_last_screenshot (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +65 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

2 tools describe read intent but their handlers mutate — fetch_labkey_page (line 813: filepath.write_text(html_content, encoding='utf-8')); mailchimp_get_campaign (line 203: html_file.write_text(html, encoding="utf-8"))

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

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

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

1 file appear obfuscated

Ship unminified, readable source.

Tool description accuracy

fetch_labkey_page: description implies read-only but handler writes/deletes/executes; mailchimp_get_campaign: description implies read-only but handler writes/deletes/executes

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