Skip to main content
Glama

pricecharting_price_history

Read-only

Get a PriceCharting product's monthly price history: one series per price column (a card's Ungraded, Grade 7, Grade 8, Grade 9, Grade 9.5 and PSA 10, or a game's Loose, Complete, New, Graded, Box and Manual) as dated prices, oldest first, plus PSA and CGC population counts by grade for trading cards. Pass the product id, its pricecharting.com address, or console and slug. Use this to chart a collectible's price over time; use pricecharting_product for the current price guide. Price data is PriceCharting's; cite it with a link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pricecharting_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPriceCharting product id from pricecharting-search or pricecharting-console (costs one extra request)
urlNoA pricecharting.com/game/<console>/<slug> product address
slugNoProduct slug, used together with console
consoleNoConsole or set slug, used together with slug

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint annotations already covering safety, the description adds valuable behavioral context: it discloses the series-per-price-column structure, oldest-first ordering, population counts, and a citation requirement. It does not mention rate limits or authentication, but those are not central here.

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 description is front-loaded with purpose and return structure, followed by input guidance and sibling routing. It is somewhat dense due to the parenthetical examples of price columns, but every sentence provides actionable information and nothing is wasted.

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 four optional parameters, full schema descriptions, and an output schema, the description supplies everything needed: what data is returned, how to identify the product, when to prefer the sibling tool, and the citation requirement. No material gaps remain.

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%, so the individual parameters are already documented. The description adds useful semantic guidance by stating that the product can be identified via id, pricecharting.com address, or console and slug together, clarifying that these are alternative lookup paths.

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 states a specific verb and resource: "Get a PriceCharting product's monthly price history." It details the returned series and population counts, and explicitly contrasts this with pricecharting_product for current price guides, making the sibling distinction clear.

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 explicitly says when to use this tool ("Use this to chart a collectible's price over time") and names the alternative ("use pricecharting_product for the current price guide"). It also explains the three acceptable identification methods, leaving no ambiguity about invocation.

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.