Skip to main content
Glama

PrecioReal

Comparar ofertas

get_product_offers
Read-onlyIdempotent

Consulta ofertas actuales de un producto identificado por el slug devuelto por search_products. Filtra por variantId para comparar una configuración exacta. Devuelve vendedor, estado, stock ("unknown" si la tienda no lo indica), fecha de comprobación, precio y envío; null significa desconocido. Incluye priceHistory: precio habitual de 90 días, mínimo y máximo de dos años del producto nuevo y si el precio de hoy es bueno.

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>"
    },
    "name": "get_product_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesslug del producto, tal como lo devuelven search_products o check_offer_url.
variantIdNoid de una de sus variantes (product.variants[].id), para ver solo las ofertas de esa configuración.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds real value by explaining the returned fields, the 'unknown' stock sentinel, the meaning of null, and what priceHistory contains (90-day usual price, 2-year min/max, good-price flag). It omits currency/tax and freshness guarantees.

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 front-loaded sentences: purpose, then filtering, then return shape, then the priceHistory detail. Dense but purposeful, with no filler; the return-value sentence is long but justified given there is no output schema.

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 the return documentation and does so thoroughly, including sentinel values and the priceHistory breakdown. Missing only peripheral details such as currency and price freshness semantics, which keeps it short of full completeness.

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% and the schema itself already documents both slug (with origin) and variantId (variant configuration filter). The description mostly restates that, adding only the comparative intent of variantId, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Consulta ofertas actuales de un producto') and pins the identifier to the slug returned by search_products. It is clearly distinguishable in intent, though it never explicitly contrasts itself with get_offer_history, which is the closest sibling.

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 gives actionable context: obtain the slug from search_products or check_offer_url, and use variantId when comparing one exact configuration. There are no explicit exclusions or a named alternative for historical rather than current pricing, so the guidance is clear but not complete.

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