Skip to main content
Glama

Card price

card_price
Read-onlyIdempotent

Use this when the user asks what one specific card or sealed product is worth today. Returns the latest daily TCGplayer market price and lowest listed price per printing (Normal, Holofoil, Reverse Holofoil, 1st Edition...) with the date of the price, in USD, plus headline (the printing and price the TickerMint page leads with) and the page URL. Raw (ungraded) prices only; not an appraisal of a particular copy. near_mint, when present, is the Near Mint price of the headline printing with its date; the market price is for any condition. When PriceCharting has the card, graded adds its PSA 10 and Grade 9 values from sold listings with the PriceCharting credit and link (every grade: graded_price). 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": "card_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesTickerMint product_id from search_cards.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / product_id / description
      Added value: +"TickerMint product_id from search_cards."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, and the description layers on real behavioral context: currency (USD), that prices are daily and dated, per-printing granularity, raw/ungraded only, and an explicit disclaimer that it is not an appraisal of a specific copy. It also clarifies the non-obvious distinction that `near_mint` is the headline printing's NM price while the market price is condition-agnostic, and that graded values come from PriceCharting sold listings with attribution.

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 trigger condition before the return-value detail, and every clause carries information about output shape or semantics. It is dense and somewhat run-on, with parenthetical printing lists and a compressed sentence about `near_mint` that takes a second read, but no sentence is filler.

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 one-parameter read tool with an output schema, this covers everything an agent needs: when to call it, the prerequisite lookup, currency and date semantics, printing granularity, and the limits of what the prices mean. The output schema handles structure, so the description's job is semantic interpretation, which it does fully.

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% and the single parameter is already documented as a TickerMint product_id from search_cards. The description repeats that provenance ('Needs a product_id from search_cards') without adding format, validation, or failure behavior beyond the schema, so the baseline of 3 applies.

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 and resource — returns the latest daily TCGplayer market and lowest listed price for one specific card or sealed product — and scopes it to a single product rather than a set or history. An agent can distinguish it from price_history, set_prices, and sealed_prices from the text alone.

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 ('when the user asks what one specific card or sealed product is worth today') and names the upstream dependency ('Needs a product_id from search_cards'), which routes the agent correctly. It does not explicitly say when to prefer price_history or graded_price instead, and the mention of a `graded` block slightly blurs the line with the graded_price sibling.

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