Skip to main content
Glama

wintraits_chequeo_rapido

Does my listing have what today's best sellers have? Quick check of a listing, a technical sheet or a draft. (¿Tiene mi ficha lo que tienen hoy los más vendidos de mi categoría?)

Every Scan category (solo_scan in wintraits_categorias_disponibles; use wintraits_buscar_categoria to find the code): a snapshot of today's best sellers against the rest, not a prediction. indice_scan is the Wintraits Scan Index (0-100: how much of the best sellers' distinguishing traits the listing has, weighting the top-ranked sellers more; 100 = the most complete best-seller listing today; puntos is the raw 0-100 score before that scaling; only the traits readable from the listing count), with the middle half of best sellers and of the rest (out of sample); null if fewer than 3 traits can be read. zona says where it falls: "mas_vendidos" (best sellers' zone), "entre" (in between), "resto" (the rest's zone) or "por_encima" (well above the best sellers: it mentions more traits than usual, and adding more does not bring it closer to them; never present it as better than the best sellers). Always name it "Wintraits Scan Index" with its best sellers' band (texto); give the user its frase and zona_frase; metodo links to how it is computed. cifras gives, for images, bullets, title and description length and price, the listing's value (tu_ficha) next to the median and middle half of best sellers and of the rest. Each trait says how often it appears among best sellers and the rest, and lo_tiene = true/false if it can be read from the listing, null if the user must check it. te_faltan lists the listing traits more frequent among best sellers that the listing lacks. indice_scan.partes splits the index into producto and presentacion (null with a motivo when it cannot be computed, never 0). The listing does not need to be on Amazon: a draft or the page of another shop works too. Match categories (disponibles) also accept it, but wintraits_diagnosticar_producto gives more.

Args: titulo: listing title. categoria: Scan category id (e.g. "hidratantes"; see wintraits_categorias_disponibles). pais: country code (e.g. "ES"). vinetas: bullet points of the listing. descripcion: listing description. num_imagenes: number of images, if known. video: whether the listing has a video, if known. precio_eur: selling price in euros, if known. ficha_tecnica: technical sheet text (no online listing), used when titulo is empty: only the product part of the index is computed; partes.presentacion comes with valor null and motivo "sin_ficha_de_tienda". 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

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

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
videoNo
tituloNo
vinetasNo
categoriaNo
precio_eurNo
descripcionNo
num_imagenesNo
ficha_tecnicaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / categoria / default
      Added value: +""
    • addedInput schema / properties / ficha_tecnica
      Added value: +{
      +  "default": "",
      +  "title": "Ficha Tecnica",
      +  "type": "string"
      +}
    • addedInput schema / properties / titulo / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
      -  "titulo",
      -  "categoria"
      -]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description supplies substantial operational detail: current rather than predictive results, score weighting, readable-trait and null-threshold rules, partial technical-sheet behavior, interpretation warnings, and the free, unlimited beta window. It falls short of exhaustive disclosure because it does not explicitly state that the check is side-effect free or identify any authentication or data-access prerequisites.

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

Conciseness3/5

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

The purpose and category routing are front-loaded, and the argument list is easy to scan. However, the central output explanation is an excessively dense wall of nested clauses and inline fields, while the Spanish question and bilingual beta statement add duplication; structured output bullets would be substantially clearer.

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 ten-parameter tool with no output schema, it unusually covers the principal result fields, score scales, null cases, presentation cautions, category discovery, alternatives, and beta limits. It nevertheless leaves the minimum valid invocation ambiguous, particularly whether `categoria` is mandatory and whether at least one of `titulo` or `ficha_tecnica` must be nonempty, even though every schema parameter is optional.

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?

Despite 0% schema description coverage, the Args section documents all ten parameters with meanings, examples, optional `if known` inputs, and the two `lang` choices. The interaction between `ficha_tecnica` and an empty `titulo`, including the resulting null presentation component and its `motivo`, adds especially valuable semantics absent from the flat schema.

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 opening defines a concrete operation: quickly checking a listing, technical sheet, or draft against today's category best sellers. It further clarifies that the result is a comparative snapshot rather than a prediction and distinguishes its depth from `wintraits_diagnosticar_producto` for Match categories.

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 directs the agent to Scan (`solo_scan`) categories, names `wintraits_buscar_categoria` for discovering the category code, and routes Match-category users wanting more depth to `wintraits_diagnosticar_producto`. It also clarifies that drafts and non-Amazon shop pages are acceptable and defines when the technical-sheet path applies.

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