Skip to main content
Glama

PrecioReal

Consultar historial de oferta

get_offer_history
Read-onlyIdempotent

Consulta el historial de una oferta exacta devuelta por get_product_offers. Requiere slug y offerId completos. Mantiene separados el vendedor y el canal de precio. Amazon se consulta mediante un enlace externo a Keepa.

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": {
      "slug": "<slug>",
      "offerId": "<offerId>"
    },
    "name": "get_offer_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDías de historial hasta hoy, de 1 a 730. Por defecto, 180.
slugYesslug del producto al que pertenece la oferta.
offerIdYesid completo de una oferta de get_product_offers (product.offers[].id), sin modificar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds genuine behavioral context — that seller and price channel are kept separate in the history, and that Amazon returns an external Keepa link rather than local history. It does not mention rate limits, time granularity, or behavior when an offer has no history.

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?

Four short sentences, each carrying a distinct fact — identity, prerequisites, output separation, Amazon exception — and the subject is front-loaded. Slight redundancy between 'exacta' and 'completos', but no filler.

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 supplies the key return-shape signals (seller vs price-channel separation, external Keepa link for Amazon) that an agent needs to interpret results. Missing detail on granularity and empty-history cases keeps it from a 5, but nothing essential for calling it correctly is absent.

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% (slug pattern, offerId length and source, days range and default are all documented), so the baseline is 3. The description only reinforces that slug and offerId must be 'completos' and untouched, and never mentions the optional days window.

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 ('Consulta el historial de una oferta exacta') and qualifies it with 'exacta' plus the provenance 'devuelta por get_product_offers', which lets an agent distinguish it from search_products or get_product_offers without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It tells the agent the prerequisite path (ids must come from get_product_offers, unmodified) and carves out a real exception: Amazon offers are not served from this history but through an external Keepa link. It stops short of explicitly naming which sibling to use for other needs, but the routing context is clear.

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