Skip to main content
Glama

Get Geizhals price history

geizhals_get_price_history
Read-onlyIdempotent

Get the best-price history of one Geizhals product by its product_id. Returns the current best price, the all-time lowest and highest best price, and the dates on which the best price changed within the chosen window (each entry is valid until the next one). Reads public data only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHistory window in days, 1 to 3650. Default: 90.
marketNoGeizhals market: de (Germany), at (Austria) or eu (EU). Default: de.
product_idYesGeizhals product id, e.g. "2795961", or a Geizhals product link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 open-world, so the safety profile is covered. The description adds real value beyond that: it enumerates the returned components (current best price, all-time min/max, change dates) and discloses the non-obvious entry semantics (each entry valid until the next) plus that only public data is read, implying no auth is required.

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 the action and scope, then the return payload, then the access constraint. No hedging, no repetition of the title, and every clause contributes information.

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 does the heavy lifting by describing the result shape, which is the key risk area for this tool. The residual gap is the ambiguity over whether the all-time extremes respect the days window, and the market parameter is 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 100%, so product_id, days and market are already documented with defaults and an enum, making 3 the baseline. The description adds only the tie between the window and which changes are reported ("within the chosen window"), and it leaves open whether the all-time low/high are window-bound or truly all-time.

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?

States a specific verb and resource ("Get the best-price history") scoped to one product identified by product_id. The resource phrase (price history) is inherently distinct from geizhals_get_product and geizhals_search_products, so an agent can route correctly 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 Guidelines3/5

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

The description establishes the input precondition (a known product_id) and the window concept, implying usage when historical prices for a specific product are needed. However, it never explicitly says when to prefer this over geizhals_get_product, nor does it state exclusions or alternatives.

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