TickerMint

Graded card prices

graded_price

Read-onlyIdempotent

Use this when the user asks what a graded (slabbed) copy of one card is worth, or how much more a PSA 10 sells for than a raw copy. Returns PriceCharting's values from sold listings for each grade it has (PSA 10, BGS 10, CGC 10, SGC 10, TAG 10 and grades 7, 8, 9 and 9.5 from any grader), its ungraded value, how many times the ungraded value a PSA 10 sells for, the date, and the credit 'Prices from PriceCharting' with a link to the card's PriceCharting page, which goes with any value quoted. Singles only; needs a product_id from search_cards.

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": {
      "product_id": "<product_id>"
    },
    "name": "graded_price"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes	TickerMint product_id from search_cards.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: the data source is PriceCharting sold listings, the response carries an attribution credit and card link that must accompany any quoted value, and coverage is limited to singles with the grades listed. That attribution obligation is a usage constraint an agent cannot infer from structured fields.

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?

Front-loads the trigger condition, then the payload, then the constraints — a sensible order with no filler. The second sentence is long and enumerates grades in a run-on list, though each element is functional information rather than padding.

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, yet the description still summarizes the return shape and, more importantly, discloses the attribution requirement and singles-only scope. For a single-parameter read tool with full annotation coverage, nothing an agent needs to select or invoke it correctly is missing.

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 100% and the single parameter already documents itself as a TickerMint product_id from search_cards; the description reinforces the dependency by requiring a product_id sourced from search_cards, tying the tool into a call sequence. No extra meaning about the ID format is added, so it is slightly above the schema-only baseline rather than well beyond it.

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+resource (returns graded/slabbed card prices by grade) and enumerates exactly what it yields: PSA/BGS/CGC/SGC/TAG 10 values, grades 7–9.5, ungraded value, the PSA 10 multiplier, date and attribution. The 'singles only' and 'graded vs raw' framing cleanly separates it from card_price and sealed_prices.

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?

Opens with an explicit trigger — 'Use this when the user asks what a graded (slabbed) copy of one card is worth' or asks about the PSA 10 premium — and states the prerequisite (a product_id from search_cards) plus a hard exclusion (singles only). It implies but never names card_price as the tool for raw-only pricing, which keeps it short of a full when/when-not routing pair.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TickerMint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?