Skip to main content
Glama

wintraits_chequeo_asin

Quick check of an Amazon listing by its ASIN or product link: we read the public listing, detect its Scan category and return the same as wintraits_chequeo_rapido. (Chequeo rápido de una ficha de Amazon por su ASIN o enlace.)

ficha_leida gives the ASIN, the detected category and where its price sits against the middle half of best sellers (por_debajo, dentro, por_encima). The listing's text and price are not returned. If the product is not in a category with Scan published, it returns an error with the available categories: then use wintraits_chequeo_rapido with the pasted listing and the closest category.

Args: asin_o_enlace: ASIN (10 characters, e.g. "B0XXXXXXXX") or Amazon product link (its country wins over pais). pais: country code when only the ASIN is given (default "ES"). lang: "es" (default) or "en".

Free and unlimited during the beta (until 2027-01-31). Gratis y sin límite durante la beta (hasta el 31-ene-2027).

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": {
      "asin_o_enlace": "<asin_o_enlace>"
    },
    "name": "wintraits_chequeo_asin"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
asin_o_enlaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that listing text and price are not returned, that out-of-category products produce an error containing available categories, and that usage is free and unlimited during the beta until 2027-01-31. It stops short of describing authentication, latency, or the full error surface, which keeps it from a 5.

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?

The first sentence front-loads purpose and the fallback rule follows immediately, so the important routing information is early. The fully duplicated Spanish/English sentences and Args prose add length without adding meaning for a single reader, costing a point but not readability.

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?

There is no output schema, yet the description names the return field (`ficha_leida`), what it contains (ASIN, detected category, price position as por_debajo/dentro/por_encima), and what it omits (listing text and price). For a 3-parameter read-only lookup this is nearly sufficient, with only the exact error payload shape left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it documents all three parameters with meaning the schema lacks: asin_o_enlace accepts a 10-character ASIN or a product link whose country overrides `pais`; `pais` is the country code used only when a bare ASIN is given (default ES); `lang` is "es" (default) or "en". This resolves the ambiguity a bare schema leaves around the ASIN-vs-link precedence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ("read the public listing" of an Amazon listing by ASIN or product link) and names the concrete outputs (detected Scan category, price position). It also explicitly equates its result with the sibling wintraits_chequeo_rapido, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: if the product is not in a category with Scan published, the tool errors and lists available categories, and in that case the caller should use wintraits_chequeo_rapido with the pasted listing and the closest category. Both the when-to-use and the fallback alternative are spelled out, with no inference required.

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