Skip to main content
Glama

Price history

price_history
Read-onlyIdempotent

Use this when the user asks whether a card's price is going up or down, how it moved over a period, or what it was worth on a past date. Returns the market price per printing in USD for the last days days (7 to 1000; history starts February 2024, later for newer cards): daily for the most recent 90 days, and one price per calendar month (the month's last recorded day) for anything older; daily prices older than 90 days are on the card's TickerMint page for members and in the TickerMint API on a plan. Past prices only, no forecasts.

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": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many recent days, 7 to 1000.
product_idYesTickerMint product_id from search_cards.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"How many recent days, 7 to 1000."
    • addedInput schema / properties / product_id / description
      Added value: +"TickerMint product_id from search_cards."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior: USD currency, per-printing granularity, daily resolution for 90 days then monthly aggregation using the month's last recorded day, history starting February 2024, and access restrictions for older daily data.

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 usage trigger and free of filler, but the middle sentence is a long, clause-heavy run that mixes return granularity, history bounds, and membership/API access. It earns its content yet could be split for faster parsing.

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?

Both parameters are documented in schema and reinforced in prose, an output schema exists so return structure need not be spelled out, and the description still explains the shape of results (daily vs monthly buckets). Nothing needed to call this 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%, so the baseline is 3, but the description adds real meaning: `days` changes output granularity (daily vs monthly), history is bounded by a February 2024 start (later for newer cards), and prices are per printing in USD. Only minor syntax detail beyond the schema is missing.

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 scope: market price per printing in USD over the last `days` days, with an explicit 'Past prices only, no forecasts' boundary. That implicitly separates it from a current-price lookup, but no sibling (e.g. card_price) is named, so the differentiation is inferred rather than stated.

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 opens with concrete user-intent triggers: price going up or down, movement over a period, or value on a past date. It also states a negative boundary ('Past prices only, no forecasts') and points to where daily prices older than 90 days live, so an agent knows the tool's limits rather than guessing.

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