Skip to main content
Glama

Findazo

Plazo y coste de envío de AliExpress por país

envio_aliexpress

Plazo de entrega mediano, porcentaje con envío gratis y coste mediano que indicaba AliExpress para una muestra de productos medidos por Findazo con la API de AliExpress (Índice Findazo, datos mensuales). Son estimaciones de AliExpress, no entregas medidas.

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": {
      "pais": "<pais>"
    },
    "name": "envio_aliexpress"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisYesPaís de destino (ISO 3166-1 alfa-2).

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?

With no annotations, the description carries the full burden and does meaningful work: it discloses data provenance (Findazo sampling via the AliExpress API), recency (monthly data), and a crucial caveat that these are AliExpress's own estimates rather than measured deliveries. It stops short of stating the cost currency, the sample size, or how the medians are computed, so it is not complete.

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 sentences, no filler, with the metric list and the caveat each getting one sentence. The first sentence is dense with parenthetical provenance, which slightly slows front-loading, but nothing is wasted.

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 one-parameter read tool with no output schema and no annotations, the description covers what an agent most needs: which three metrics come back, that data is monthly and sample-based, and that values are AliExpress estimates. Missing details such as currency and whether results break down per product keep it from a 5.

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%: the single 'pais' parameter is typed, enum-constrained to ten countries, and documented as ISO 3166-1 alpha-2. The description adds nothing about the parameter beyond confirming the data is per country, 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 names the exact metrics returned (median delivery time, share with free shipping, median cost) and the source (AliExpress via the Findazo API, monthly). That is far more specific than restating the title. It never references the sibling 'ideas_regalo', so it does not differentiate itself from alternatives, which keeps it below a 5.

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?

Use is only implied: an agent can infer it retrieves AliExpress shipping estimates for a destination country. There is no explicit when-to-use, no when-not-to-use, and no pointer to the only sibling tool for agents unsure whether this or 'ideas_regalo' fits.

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