Skip to main content
Glama
Procurement MCP

Procurement MCP

by belikh

get_price_history

Retrieve Amazon price history for one product from Keepa: current price plus 30-day, 90-day, and all-time low and high, with an optional full series of price changes over a chosen window.

Instructions

Amazon price history for one product, from Keepa.

Returns current, 30-day and 90-day average, and all-time low and high for
the price sold by Amazon itself. Needs KEEPA_API_KEY and KEEPA_DOMAIN.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWindow for the price series
include_seriesNoAlso return every price change in the window. Default: summary only.
offer_id_or_asinYesAn amazon_au offer id (amazon_au:B0XXXXXXXX) or a bare ASIN

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the definition carries the full burden and does reasonably well: it names the external dependency (Keepa), the required credentials (KEEPA_API_KEY, KEEPA_DOMAIN), and the exact metric scope (current, 30/90-day average, all-time low/high) for a specific price type. It stops short of rate limits, error behavior, or what happens when a product has no Keepa record.

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?

Three short lines, front-loaded with the core purpose before the return contents and then the dependency. Near-zero waste; the only nit is that the metric list is stated as fixed when the days parameter makes it configurable.

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?

Since an output schema exists, return-shape explanation is not required, and the definition covers the material external facts an agent needs — provider, credentials, and price-type scope. Adequate for a 3-parameter read tool; only edge-case and failure behavior are unaddressed.

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 100%, so the schema already documents offer_id_or_asin, days, and include_series, making 3 the baseline. The description adds no information about the days window or the series toggle, and its fixed "30-day and 90-day average" framing sits slightly awkwardly against a configurable 1-365 day window, but the schema resolves the ambiguity.

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+source: "Amazon price history for one product, from Keepa." The single-product scope plus the explicit "price sold by Amazon itself" qualifier makes it distinguishable from the broader search siblings, 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?

Usage is only implied — the definition establishes single-product scope and the Amazon-sold price dimension, which implies when it fits, but there is no explicit when-to-use, no exclusion, and no pointer to get_offer_detail or search_history as alternatives. An agent must infer routing from scope alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.