v0.1.14: MCP tool annotations and honest side-effect disclosures
0.1.14: MCP tool annotations and honest side-effect disclosures
Glama's TDQS reads the schema, not just the prose: every tool now carries
MCP annotations, and the nine tools it scored C got descriptions that say
what they do to the page, the disk and later calls.
- annotations on all 33 tools: readOnlyHint for observation, and
destructiveHint=true where a call can overwrite or remove state
(browse, goal, close_page, fill_form, press_key, drag, upload_files,
read_js); idempotentHint=false where a repeat is not a no-op
(screenshot/heap_snapshot write timestamped files, scroll is relative,
trace_start/stop change session state) - read_js is documented as arbitrary JavaScript, not observation: its
annotation set is no longer read-only - lighthouse: readOnly=false (npx fetches and runs a second Chrome), and
it resolves the current URL through on_page instead of crashing when no
browser has started yet - dialog_policy, upload_files, route, emulate, select_page, resize, drag,
heap_snapshot: descriptions now state persistence, replacement and
error conditions - tests pin the full 33-tool annotation table over the real stdio protocol