Skip to main content
Glama

Get price history

get_price_history
Read-onlyIdempotent

Read observed daily history, its series basis, currency, condition and sample counts. Dates are UTC. Missing days are gaps, not interpolated prices. Follow service pagination. Use list_offers instead for the latest observed offers and links; use list_price_drops instead to find listings in a market whose observed price fell.

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": {
      "variant_id": "<variant_id>",
      "market_id": "<market_id>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoUTC date YYYY-MM-DD; defaults to today
fromNoUTC date YYYY-MM-DD; defaults to 366 days before to
limitNoDefault 60; maximum 100
cursorNo
market_idYes
variant_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: dates are UTC, missing days are gaps rather than interpolated prices, and pagination must be followed. It stops short of describing limits or response envelope details, which keeps it at a 4 rather than a 5.

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 scoping and data-semantics constraints are front-loaded before the alternative routing, and every sentence carries information. The opening sentence is somewhat compressed ('its series basis, currency, condition') and reads as a list rather than flowing prose, which costs a point.

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 an output schema present, return values need not be explained, and the description covers the non-obvious parts: timezone, gap semantics, and pagination. It is nearly complete for a 6-parameter read tool; only identification of variant_id/market_id and the limit ceiling are left entirely to the schema.

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 50%; from/to/limit are documented in the schema and the description only reinforces the UTC basis and the pagination intent behind cursor. The three undocumented parameters (variant_id, market_id, cursor) get no added meaning from the description beyond a passing mention of pagination, so it partially compensates but leaves real gaps.

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 ('Read observed daily history') plus the shape of what comes back ('series basis, currency, condition and sample counts'). It explicitly names the two sibling tools it is not, so an agent can distinguish it from list_offers and list_price_drops without opening the schema.

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?

Explicit routing rules are given with the condition that selects each alternative: use list_offers for the latest observed offers and links, list_price_drops to find listings whose observed price fell. The implicit case (this tool for the historical daily series) is unambiguous from the first sentence.

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