Skip to main content
Glama

submit_report

Use this for any follow-up that already thinks of the call as submit_report; prefer grade_card, which is the same tool. Deprecated alias of grade_card: front and back JPEG, PNG, or WebP data URLs required (min 250px, keep under ~350KB). The report is an estimate, not a PSA, CGC, or BGS grade. $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": "submit_report"
  }
}

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.3/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: cost ($0.30 per successful report, $0.25 at wallet balance ≥ $250.00), throttling (10 per minute, 2 in flight), the deprecation status, and the explicit caveat that the result is an estimate rather than a graded slab. These are exactly the operational facts an agent needs before spending money.

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?

The routing/deprecation guidance is correctly front-loaded ahead of the constraints, and every clause carries information (preference, deprecation, image format, pricing, rate limits). The opening clause about 'any follow-up that already thinks of the call as submit_report' is slightly circular, and the single dense paragraph could be split, costing it a point.

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 paid, rate-limited image-submission tool with an output schema (so return shape need not be explained), the description covers deprecation, cost, throttling, and input constraints. Remaining gaps are minor: it does not say what happens on a failed submission or whether the wallet must be funded before calling.

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 all three parameters including idempotency_key are already documented in the schema. The description's image notes (JPEG/PNG/WebP data URLs, min 250px, under ~350KB) largely restate the schema and omit the idempotency key entirely, so it adds little beyond the structured fields — baseline 3.

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 states plainly that this is a 'Deprecated alias of grade_card' and that the output 'is an estimate, not a PSA, CGC, or BGS grade', which lets an agent distinguish it from get_report, get_report_pdf, and the pricing tools. What is only inferable is the underlying action (submitting front/back card photos for an automated condition estimate) — the verb is never stated outright, so it stops short of a 5.

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?

Routing guidance is explicit and conditional: 'Use this for any follow-up that already thinks of the call as submit_report; prefer grade_card, which is the same tool.' That names the alternative, the preference, and the narrow case where this alias applies — nothing is left to inference.

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