Skip to main content
Glama

PrecioReal

Comprobar enlace de tienda

check_offer_url
Read-onlyIdempotent

Comprueba el enlace de un producto en una tienda española: devuelve su ficha de PrecioReal con las ofertas de otras tiendas para la misma variante y priceHistory. checkedLink.offerIds identifica la oferta del enlace.

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": {
      "url": "<url>"
    },
    "name": "check_offer_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesEnlace a la página de un producto en una tienda española, con https://.

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 the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds real value beyond them by disclosing the return payload: a PrecioReal record, offers from other stores for the same variant, priceHistory, and the meaning of checkedLink.offerIds. It does not say what happens for unsupported, non-Spanish, or non-product URLs, which is a notable gap for an open-world fetch.

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?

Two compact sentences: the action and return shape come first, with the checkedLink.offerIds detail as a follow-up. Nothing is redundant, though the trailing field reference is terse enough to be slightly opaque about the response envelope.

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 must carry return-value information, and it does so adequately (PrecioReal record, competing offers, priceHistory, offer ID location). Given one well-documented parameter and rich annotations, the only meaningful omission is failure behavior for invalid or unsupported links.

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?

There is a single parameter with 100% schema description coverage, and the schema already states it must be a product page URL with https://. The description restates the same constraint ('enlace ... en una tienda española') without adding format or edge-case detail, 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 ('Comprueba el enlace de un producto en una tienda española') and goes on to describe the result: the PrecioReal record with cross-store offers and priceHistory. The URL-based input implicitly separates it from siblings like search_products or get_product_offers, though no sibling is named 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?

Usage is implied by the input: call this when you already hold a product URL from a Spanish store. There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives (e.g. search_products when you have no URL, or get_offer_history for price trends), so the agent must infer the boundary.

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