Skip to main content
Glama

Card price history

card_history
Read-only

PokéItem fair-value history (EUR) for a card, up to 30 days, unlimited/NORMAL only. 1st-edition is not historized — do not treat unlimited history as an ED1 trend. Marketplace comps are never included.

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": {
      "cardId": "<cardId>"
    },
    "name": "card_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYes
versionNoIf FIRST_EDITION, returns no points plus an explicit note.
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a safe read-only, closed-world operation, so the description correctly spends its words on data-coverage behavior: 30-day maximum, EUR denomination, unlimited/NORMAL editions only, no first-edition historization, and exclusion of marketplace comps. These constraints materially change how an agent interprets results. It does not say what an empty or short series looks like beyond the first-edition case, which is covered in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, each carrying distinct information, with the most important constraint (30-day, unlimited-only, EUR) front-loaded. No filler and no restatement of the tool name. Minor jargon ("ED1", "comps") is decodable from immediate context.

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?

With no output schema, the description still conveys the return shape (a points series over up to 30 days, in EUR) and the notable empty-result case for first editions. What is missing is the meaning of the `language` parameter and any hint about series granularity or sparsity, which matter for a time-series tool.

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 only 33% (only `version` is annotated), so the description must compensate and it partly does: "unlimited/NORMAL only" and "1st-edition is not historized" give real meaning to the `version` parameter beyond the schema note. However, `cardId` format/source and `language` (presumably which market's price series is used) are left entirely unexplained in both schema and description.

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 names a specific resource and output type: fair-value price history in EUR for a single card, capped at 30 days. It clearly distinguishes this from a current-price lookup by being a history endpoint. It stops short of naming sibling tools (lookup_card, deal_check) that an agent might otherwise pick, so it is clear but not sibling-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is for trend analysis of a card's value. The one explicit instruction is interpretive ("do not treat unlimited history as an ED1 trend"), which is a caution, not a when-to-use rule. No alternative tool is named for cases where the agent needs current price or a marketplace comp.

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.