Skip to main content
Glama

PDF report link

deep_pdf
Idempotent

Get a download link for the PDF report of a finished deep research run (status done), to hand the user a shareable document. Free plans get a watermarked copy.

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": {
      "id": "<id>"
    },
    "name": "deep_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: the finished-status gate and the free-plan watermarking of the returned copy. However, it says nothing about link lifetime or whether fetching the link triggers PDF generation, and the non-read-only annotation (readOnlyHint=false) is left unexplained by a description that reads like a pure fetch.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the action and resource, then the precondition, then the user-facing benefit and the plan caveat. Nothing is redundant.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers the input, availability precondition, and the nature of the returned artifact (a shareable, possibly watermarked PDF link). Link expiry and permission requirements are the remaining gaps.

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

Parameters4/5

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

Schema coverage is nominally 100%, but the schema entry is a vacuous "id" with no explanation; the description compensates by making clear it is the identifier of a finished deep research run. With a single parameter this is adequate, though it does not state the expected format of that 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?

States a specific verb and resource ("Get a download link for the PDF report") plus the precondition that the run must be finished (status done). It clearly is not deep_events or get_deep_analysis, but it never names an alternative, so differentiation is implicit rather than explicit.

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

Usage Guidelines4/5

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

Gives a clear triggering condition (only for runs with status done) and a purpose (hand the user a shareable document). It stops short of exclusions, such as what to do for a run still in progress or whether another tool yields the raw report.

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.