Skip to main content
Glama

Findazo

Ideas de regalo de AliExpress con precio por país

ideas_regalo

Productos de AliExpress de las guías de regalo de Findazo, elegidos con datos (valoración de 4,6 o más y al menos 300 ventas en 180 días), con su precio en el país indicado y la fecha de consulta. Devuelve enlaces a las páginas de Findazo.

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": "ideas_regalo"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNoPaís del comprador (ISO 3166-1 alfa-2). Por defecto ES.
limiteNoMáximo de resultados (por defecto 8, máx. 20).
para_quienNoTipo de regalo. Por defecto, general.
presupuestoNoPrecio máximo en la moneda del país (EUR en ES, MXN en MX, GBP en GB, USD en US…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses useful selection criteria (rating of 4.6 or higher and at least 300 sales in 180 days), country-specific price display, query date, and that it returns Findazo page links, but it does not explain result limits, empty-result behavior, caching, or freshness beyond the query date.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the core product source, and packs the selection criteria into a compact parenthetical. It contains no filler and places the return behavior in a short final sentence.

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?

For a four-parameter read tool with full schema coverage but no output schema, the description covers the source, selection criteria, country price, query date, and high-level return value. It still lacks detail on returned product fields or result-list structure, so it falls slightly short of complete output context.

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 all four parameters. The description adds only implicit context that the country parameter affects price display and that results are curated, without adding syntax or behavior beyond the schema.

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 clearly states that the tool returns AliExpress gift ideas from Findazo's gift guides, selected using rating and sales thresholds, with prices by country and query date. It is specific about the resource and filtering logic, but it does not explicitly distinguish itself from the sibling tool envio_aliexpress.

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 references to gift guides, country-specific pricing, and selection criteria, so an agent can infer this is for gift recommendation queries. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison with alternatives.

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