Skip to main content
Glama

get_report

Use this for any follow-up after a grading report was started and you need the finished grade, centering, defects, prices, or PSA population. Poll until the status is completed or failed. Polling itself is not charged, and a failed report releases the hold. Free, limited to 120 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesReport UUID

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.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that polling is not charged, that a failed report releases the hold, that the call is free, and that there is a 120/minute rate limit. These are the exact operational facts an agent needs before looping on a paid-job endpoint.

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?

Three short sentences, front-loaded with the use case, then the polling instruction, then the cost/limit constraints. Nothing is wasted, though the opening clause 'Use this for any follow-up after...' is slightly wordier than a direct 'Get the finished grading report'.

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

Completeness5/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 the remaining gaps for a polling-style tool: cost, rate limit, terminal states, and hold release on failure. Nothing an agent needs in order to call and loop on this tool is missing.

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?

There is a single parameter (report_id) with 100% schema description coverage, so the schema already documents it as a Report UUID. The description adds no additional meaning about the identifier, which is the expected baseline 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?

Names a specific resource (a grading report) and enumerates exactly what it yields: finished grade, centering, defects, prices, PSA population. The framing 'follow-up after a grading report was started' implicitly separates it from submit_report, which starts the job, and the returned field list separates it from get_report_pdf.

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 an explicit trigger condition ('any follow-up after a grading report was started') and an explicit operating loop ('Poll until the status is completed or failed'). It does not name a competing sibling such as get_report_pdf for document retrieval, so it stops short of full when-not guidance.

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