get_reportRead a report by its slug without waiting, with provider placement so far.
Works for one-hour tests and for letters in the person's series mailboxes.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The slug of a test or of a letter in a series mailbox, the last part of the report URL. |
| Name | Required | Description | Default |
|---|---|---|---|
| view | Yes | test, report, mailbox, mailboxes, series or error |
Changes observed during successful MCP inspections.
Input schema / properties / slug / descriptionPrevious value: -"The slug of a test, the last part of the report URL."New value: +"The slug of a test or of a letter in a series mailbox, the last part of the report URL."Output schema / additionalPropertiesAdded value: +trueOutput schema / descriptionAdded value: +"What every tool returns for the card; `view` says which card."Output schema / properties / resultRemoved value: -{
- "title": "Result",
- "type": "string"
-}Output schema / properties / viewAdded value: +{
+ "description": "test, report, mailbox, mailboxes, series or error",
+ "title": "View",
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "result"
-]New value: +[
+ "view"
+]Output schema / titlePrevious value: -"get_reportOutput"New value: +"Output"Input schema / properties / slug / descriptionAdded value: +"The slug of a test, the last part of the report URL."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description adds genuinely useful behavior the annotations don't encode — it returns immediately rather than blocking, and results may be partial ('so far'), which warns the agent about incomplete placement data.
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?
Two short sentences, front-loaded with the action and the key non-blocking property. No waste, though the second sentence's phrasing is slightly awkward rather than maximally crisp.
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?
An output schema exists, so return values need not be described; the description supplies the valid scope (one-hour tests, series-mailbox letters) and the non-blocking/partial-result behavior. Together with the annotations, an agent has everything needed to call it correctly.
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?
Schema description coverage is 100% and the single slug parameter is fully documented in the schema, including the 'last part of the report URL' hint. The description adds nothing beyond 'by its slug', so the baseline 3 applies.
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?
States a specific verb (read) and resource (report) keyed by slug, and the 'without waiting' clause implicitly separates it from the sibling wait_for_report. The phrase 'with provider placement so far' is cryptic and adds little clarity, but the core purpose is unambiguous.
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?
'Without waiting' hints at the non-blocking alternative (wait_for_report) but never names it or states an explicit condition for choosing one over the other. The scope note ('one-hour tests' and 'letters in the person's series mailboxes') does tell the agent what kinds of slugs are valid.
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.