Skip to main content
Glama

Optionally download the transmitted PDF

download_transmitted_pdf
Read-onlyIdempotent

Optional after delivery: retrieve the PDF produced by the backend fax provider as an embedded PDF resource.

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_transmitted_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
fax_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does add two useful facts beyond the annotations: the call is optional and only meaningful after delivery, and the result is an embedded PDF resource from the backend provider. It stops short of describing failure behavior when no PDF exists.

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 front-loaded sentence with the precondition first and the result second, with no filler. The word 'optional' is duplicated from the title, which is mild redundancy but not damaging.

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 full annotations this is close to adequate, and the description does hint at the return form despite no output schema. The gaps are the undocumented fax_id semantics and the absence of any statement about what happens when no transmitted PDF exists.

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% for the single fax_id parameter, so the description carries the full burden and does not meet it. It never explains what fax_id identifies, whether it must refer to a successfully delivered fax, or what error results from an undelivered or unknown ID.

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 (retrieve) and resource (the PDF produced by the backend fax provider), making the action concrete rather than tautological. It implicitly separates itself from download_delivery_record and get_pdf_upload_status by scoping to the provider-generated, transmitted PDF, but it never states that distinction explicitly.

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?

'Optional after delivery' gives one real precondition for when this tool is appropriate, which is more than nothing. However, there is no guidance on when NOT to call it (e.g. before delivery, or when a delivery record is preferred instead), and no sibling is named as an alternative.

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