The consolidated patch of an audit: block to paste, files to create and templates with placeholders. No model — only facts from the page.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Audit ID, from `Audit.id`. | |
| guest_token | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / id / descriptionAdded value: +"Audit ID, from `Audit.id`."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not clearly state whether the operation is read-only or has side effects. The phrase 'No model — only facts from the page' hints at deterministic behavior but does not explicitly disclose the tool's behavioral guarantees.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and mostly to the point, using a compact structure that conveys the output contents. The 'No model — only facts from the page' line is somewhat cryptic but does not add excessive verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains what the returned patch contains and hints at its origin, but it lacks detail on the required guest_token parameter and does not clarify the intended use case relative to other audit-related tools. Overall, it is adequate but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one of two parameters (id) is described in the schema, and the description adds no additional meaning for guest_token. With 50% parameter coverage, the description should compensate for the undocumented parameter but does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as retrieving a consolidated patch for an audit, with a specific verb ('get') and resource ('patch of an audit'). The mention of 'head block', 'files to create', and 'templates' gives useful context, though the phrase 'No model — only facts from the page' is somewhat ambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus alternatives like get_audit or other sibling tools. The description implies its purpose but does not state conditions or provide comparison to related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools relate to auditing (audit_url, get_audit, run_tab) which might cause confusion, but descriptions clarify the differences. Overall, there is some overlap but each has a distinct role.
Most tools follow verb_noun pattern, but a few (billing, contact, health, api_index) are plain nouns, making the naming inconsistent.
With 14 tools, the server covers core audit functionality plus auxiliary features like billing and health, which is appropriate for its scope.
The server provides tools for auditing URLs, managing tabs, retrieving results, patches, badges, and listing tools. Missing delete/update operations for tabs or audits, but these are not critical for a page audit service.