Skip to main content
Glama

PrecioReal

Buscar productos

search_products
Read-onlyIdempotent

Busca por marca, modelo o categoría en el catálogo de PrecioReal. Usa query con términos del producto, y maxPrice para un presupuesto en EUR sobre el precio sin envío. Devuelve slugs reales para consultar ofertas. offset permite continuar desde nextOffset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoMarca, como «Sony» o «Apple», para dejar solo sus productos.
limitNoNúmero de productos, de 1 a 12. Por defecto, 8.
queryNoLo que busca el usuario: marca, modelo o tipo de producto, como «Sony WH-CH720N» o «cafetera superautomática».
offsetNoPara seguir una búsqueda: el nextOffset de la respuesta anterior.
categoryNoCategoría del catálogo, como «Móviles y smartphones» o «Cafeteras».
maxPriceNoPresupuesto máximo en EUR, comparado con el precio sin envío.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds real value on top: that results are real slugs usable for offers, that maxPrice compares against pre-shipping prices, and that offset continues from nextOffset. It omits limits such as the 12-result cap and any rate-limit behavior.

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, front-loaded with the search scope before parameter hints and the return-value note. Nothing is padded, though the parameter sentence overlaps with what the schema already says.

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 usefully discloses that results are slugs for offers and how pagination continues. For a six-parameter read-only search that is adequately complete, with only edge cases like result caps left unstated.

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 all six parameters are already documented, including the shipping-excluded price comparison and the nextOffset continuation. The description largely restates that schema text rather than adding new semantics, so the baseline 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?

States a specific verb and resource: searches the PrecioReal catalog by brand, model or category. It also hints at the downstream step ('Devuelve slugs reales para consultar ofertas'), which differentiates it from get_product_offers, though it never names that sibling explicitly.

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?

Gives some implicit usage context — use query for product terms and maxPrice for a EUR budget — and hints that returned slugs feed an offers lookup. It never states when not to use this tool, nor names an alternative to route to, leaving selection guidance inferred.

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