Skip to main content
Glama

grade_card

Use this for any question that asks you to grade a trading card from photos. Prefer this name; submit_report is a deprecated alias of the same paid report (front and back photos required). It returns identity, a condition estimate (not a PSA/CGC/BGS grade), centering, defects, prices, and PSA population. $0.30 per successful report ($0.25 when the wallet balance is at least $250.00), limited to 10 per minute and 2 in flight.

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": {
      "front": "<front>",
      "back": "<back>"
    },
    "name": "grade_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
backYesRequired. JPEG, PNG, or WebP data URL (data:image/jpeg;base64,...). Each side at least 250px, at most 4000px; keep each photo under 342KB (hard cap 684KB).
frontYesRequired. JPEG, PNG, or WebP data URL (data:image/jpeg;base64,...). Each side at least 250px, at most 4000px; keep each photo under 342KB (hard cap 684KB).
idempotency_keyNoUnique retry key so a network retry does not start a second paid report.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / back / description
      Previous value: -"Back photo as a data:image/jpeg;base64,... URL"New value: +"Required. JPEG, PNG, or WebP data URL (data:image/jpeg;base64,...). Each side at least 250px, at most 4000px; keep each photo under 342KB (hard cap 684KB)."
    • changedInput schema / properties / front / description
      Previous value: -"Front photo as a data:image/jpeg;base64,... URL"New value: +"Required. JPEG, PNG, or WebP data URL (data:image/jpeg;base64,...). Each side at least 250px, at most 4000px; keep each photo under 342KB (hard cap 684KB)."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Unique retry key"New value: +"Unique retry key so a network retry does not start a second paid report."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/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 behavioral burden and does so well: it discloses the paid nature, exact cost and discount threshold, rate limits, required photo inputs, the contents of the report, and the important caveat that the condition estimate is not a professional grade. These are exactly the operational facts an agent needs before calling a paid endpoint.

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?

The description is front-loaded with the primary instruction and then efficiently layers in the deprecated alias, report contents, pricing, and rate limits. Every sentence supplies actionable information, and there is no redundant wording.

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?

Given the existence of an output schema, the description is complete: it covers selection guidance, deprecation of the alias, required inputs at a high level, output contents, cost model, and rate limits. Nothing material is omitted for an agent deciding whether and how to call this paid grading tool.

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 description coverage is 100%, so the schema already documents front, back, and idempotency_key thoroughly. The description only restates that front and back photos are required and does not add syntax, format, or constraint detail beyond the schema, making the baseline score appropriate.

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?

The description opens with a specific verb and resource: grade a trading card from photos. It explicitly distinguishes the tool from its deprecated alias submit_report, so an agent can identify it 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?

It states exactly when to invoke this tool (any question asking to grade a card from photos), names the correct tool to prefer over the deprecated alias, and notes that front and back photos are required. No meaningful ambiguity remains for tool selection.

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