Provide basics about all available reports.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| tool name | Yes | ||
| this request | Yes | ||
| tool collection | Yes | ||
| response content | Yes | ||
| response metadata | Yes | ||
| URLs of similar requests for web users | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds modest context about returning 'basics' and covering 'all available' reports, but it does not disclose additional behaviors like pagination, permissions, or output shape beyond what annotations imply.
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 a single, direct sentence with no filler or repetition. It front-loads the key information about scope ('all available reports') and result type ('basics').
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?
For a parameter-less read-only listing tool with an output schema and strong annotations, the description is largely sufficient. The main gap is that 'basics' is slightly vague, but the output schema can clarify return values, so the description does not need to enumerate fields.
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?
The tool has zero parameters, so the description does not need to explain parameter meaning. The baseline of 4 for a parameter-less tool applies here, and the description adds no conflicting or confusing parameter-related information.
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 states a clear verb ('Provide') and resource ('basics about all available reports'), which conveys an overview-list purpose. It is distinguishable from the sibling getReport by the word 'basics' and 'all available', though it does not explicitly call out the difference from other list* siblings.
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 guidance on when to use this tool versus alternatives. It implies use when you need an overview of all reports, but it does not mention getReport for detailed single-report retrieval or explain exclusions.
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.
Each tool has a distinct purpose: getReport retrieves full reports, listReports lists them, listIssues drills into issues, listViolators details elements, listDiagnoses details diagnoses, and the request* tools handle test/future actions. No two tools overlap.
All tools follow a consistent verb_noun camelCase pattern: get or list for retrieval, request for actions. The naming is uniform and predictable.
Eight tools fit the domain well—covering listing, retrieval, drilling down, and requesting actions without redundancy or bloat.
The surface covers the full testing workflow: request a test/retest, list/get reports, inspect issues, violators, and diagnoses. No critical operations are missing.