Skip to main content
Glama

Get price history

get_history
Read-onlyIdempotent

Price change points of a SKU over the last N days (default 90): each row is when a price started to hold, with USD/EUR and the FX rate used. Rows are change points, not daily samples. Returns an error object for an unknown id.

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": {
      "sku_id": "<sku_id>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1 to 90 (the free window; longer per-SKU history is part of the paid API plans)
sku_idYesSKU id as returned by search_skus

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 declare it a safe, idempotent, closed-world read. The description earns credit beyond that by disclosing the row model (change points with hold-start semantics), the currency/FX-rate payload per row, and the error-object behavior for an unknown id — context an annotation cannot convey.

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 short sentences, front-loaded with what the tool returns, then the crucial row-model clarification, then the error case. Nothing is redundant or padded.

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 carries return-value explanation and does so at a high level (row granularity, currency pair, FX rate, error object). Minor gaps remain — row ordering and pagination/limit behavior are unstated — but the essential shape is clear for a two-parameter read 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 coverage is 100%, so the schema already documents sku_id (as returned by search_skus) and the 1-to-90 day bound. The description restates the default window but adds no parameter syntax or constraint detail beyond the schema; the currency/FX mention describes output rows, not inputs.

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?

States a specific verb+resource: price change points of a SKU over a look-back window. The clause 'change points, not daily samples' implicitly separates it from a current-price tool like get_price or a raw time-series, though no sibling is named directly.

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?

The window semantics ('last N days, default 90') imply when the tool applies, but there is no explicit guidance on when to prefer it over get_price, changes_since, or list_changes, and no stated exclusions.

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