Skip to main content
Glama

Download the delivery record

download_delivery_record
Read-onlyIdempotent

After delivery, retrieve Edwyna’s formal PDF record of the final delivered status and fax details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fax_id": "<fax_id>"
    },
    "name": "download_delivery_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
fax_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description usefully adds the post-delivery precondition and the record's contents, but says nothing about what happens if the fax has not yet been delivered or how the PDF is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the timing condition front-loaded ahead of the payload description. No redundant restatement of the tool name or annotations; 'Edwyna's formal' is the only slightly padded phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description does well to enumerate the returned content (delivered status and fax details). It is still thin on edge-case behavior before delivery and on the return medium (file bytes versus a link), which an agent would need for error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for fax_id, yet it never mentions the parameter at all. Only the 'After delivery' clause indirectly hints that fax_id must reference a delivered fax; the UUID format and required status are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('retrieve ... formal PDF record') and narrows scope with the 'After delivery' condition, so an agent knows this returns a post-delivery artifact. It stops short of differentiating itself from the similarly named sibling download_transmitted_pdf, so an agent must infer which PDF variant it needs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'After delivery' implies a timing precondition, which is useful context for when the tool is callable. However, no alternative is named and there is no when-not guidance (e.g., what to use before delivery, or when the sibling PDF tool applies), leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources