Skip to main content
Glama

get_prices

Use this for any question about what one trading card is worth. raw_nm is the TCGplayer near mint market price; raw_pc is the PriceCharting ungraded average sale; graded is PriceCharting sold comps by vendor and grade, all USD, with source, as_of, and a stale flag. A card with no stored prices is still a successful free lookup; PSA 9.5 is omitted because PSA does not issue that grade. Free, limited to 60 per minute and 1000 per key per UTC day, shared with the other free catalog calls.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCatalog card UUID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / card_id / format
      Added value: +"uuid"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Prices in USD with numeric price_usd, currency, source, as_of, and stale.",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/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 the call is free, rate-limited to 60/min and 1000 per key per UTC day shared across free catalog calls, and that an empty price set is still a successful (non-error) lookup. It also explains data provenance (source, as_of, stale flag), currency (USD), and a deliberate gap (PSA 9.5 omitted because the grade doesn't exist).

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-loaded with the use case, then field definitions, then limits — a sensible ordering with no filler. It is dense and a few clauses (the PSA 9.5 note, the rate-limit sentence) are lengthy, but each conveys actionable constraint information rather than restating structured data.

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?

For a single-parameter price lookup with an output schema and no annotations, the description covers everything an agent needs: when to call it, what each returned field means, currency, staleness signaling, quota, and the empty-result edge case. No material behavior is left undisclosed.

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% with a single card_id parameter, so the schema already documents the input. The description reinforces that this is a single-card lookup but adds no format or semantics beyond what the schema provides, making the baseline 3 appropriate.

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 opens with a specific verb+resource framing: 'any question about what one trading card is worth', and then enumerates the exact price fields returned (raw_nm, raw_pc, graded). It is clearly distinguishable from batch/population/report siblings by the 'one trading card' scope, though it never names get_prices_batch as the multi-card alternative.

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 use condition: 'Use this for any question about what one trading card is worth', which effectively routes single-card pricing questions here. It does not state a when-not condition or name the batch sibling, so the boundary for multi-card lookups is only implied by the word '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