Skip to main content
Glama

get_report_pdf

Use this for any request for a PDF of a finished TCGdetect grading report. Call it only after get_report says the report is completed. You are charged only when the PDF is returned. $0.05 per success, limited to 30 per minute.

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": {
      "report_id": "<report_id>"
    },
    "name": "get_report_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesReport UUID
idempotency_keyNoUnique retry key

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the billing model ('charged only when the PDF is returned', '$0.05 per success') and a rate limit ('limited to 30 per minute'). Those are exactly the cost and throttling traits an agent needs before calling a metered tool, and they cannot be inferred from the schema.

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?

Three short sentences, each carrying distinct load: purpose, gating precondition, cost and rate limit. The precondition is front-loaded right after the purpose, which is the correct order for a dependent call.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, precondition, cost, and throttling. The one gap is failure behavior — what happens if the report is not completed or if the rate limit is hit — though the output schema likely covers error shapes.

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

Parameters3/5

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

Schema coverage is 100%, so report_id ('Report UUID') and idempotency_key ('Unique retry key') are already documented. The description adds no further meaning about either — notably it never explains how the idempotency key interacts with the per-success charge on retries. Baseline 3 applies when the schema does the work.

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

Purpose5/5

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

States a specific verb and resource ('PDF of a finished TCGdetect grading report') and implicitly scopes it against get_report, which returns the report itself. An agent can distinguish this artifact-fetching tool from the sibling report tools without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition and names the sibling that gates it: 'Call it only after get_report says the report is completed.' That is a concrete when-to-use rule, not an implied one.

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