Skip to main content
Glama

wintraits_atributos_ganadores

Which attributes do winning products have? What should my product or listing include? (¿Qué atributos tienen los productos que triunfan? ¿Qué debe llevar mi producto o mi ficha?)

Match categories (see wintraits_categorias_disponibles, disponibles; e.g. serums on Amazon Spain): attributes and 2-3 attribute combinations that set the winning launches of a category apart. For Scan-only categories use wintraits_scan_perfil. Useful beyond Amazon too: to design a product, brief a manufacturer or write the page of an own shop or another marketplace (measured on Amazon: a reference, not proof elsewhere).

Each row has the lift (how many times more frequent among winners), the lift when checked against products launched later, the products behind it and the share of products with that attribute that end up winning. tramos explains what "bajo" (low), "medio" (medium) and "alto" (high) mean for numeric variables. On the free plan you see the attribute with the most effect and how the strongest combination starts (combinacion_mas_fuerte); bloqueado says how many more the full list has and acceso which view was used.

Args: categoria: subcategory (see wintraits_categorias_disponibles; e.g. "serums"). pais: country code (see wintraits_categorias_disponibles; e.g. "ES"). max_resultados: rows per list (1-50). lang: "es" (default) or "en" (attribute names in English).

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_atributos_ganadores"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaNoserums
max_resultadosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 carries the burden and does much of it: it names every output field (lift, later-launch lift, product counts, winner share, tramos, combinacion_mas_fuerte, bloqueado, acceso), discloses free-plan truncation, and warns that Amazon measurements are "a reference, not proof elsewhere." It stops short of error/permission behavior, but the pricing/limits note ("Free and unlimited during the beta until 2027-01-31") covers the main operational constraint.

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?

Content is front-loaded and dense, but the bilingual question pair and the duplicated beta clause in Spanish ("Gratis y sin límite durante la beta") take space without adding selection signal. The body paragraph mixing output semantics, free-plan limits and cross-marketplace caveats could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return values — and it defines every field an agent will encounter, including what bloqueado and acceso mean on the free plan and what tramos labels signify for numeric variables. For a read-only lookup on a truncated free tier, nothing essential is missing.

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

Parameters4/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 four args: categoria as a subcategory with a pointer to wintraits_categorias_disponibles, pais as a country code with an example, max_resultados with the 1-50 range that the schema lacks, and lang's "es"/"en" values with the "es" default. The separation between categoria and pais is slightly loose (both defer to the same lookup tool) but usable.

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?

"Which attributes do winning products have?" plus "attributes and 2-3 attribute combinations that set the winning launches of a category apart" states a concrete resource and the exact unit returned. It explicitly distinguishes itself from the sibling wintraits_scan_perfil for Scan-only categories and points at wintraits_categorias_disponibles for category matching.

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 the selection rule (match a subcategory such as "serums" in country "ES"), the alternative route ("For Scan-only categories use wintraits_scan_perfil"), and the non-obvious downstream uses (designing a product, briefing a manufacturer, writing a marketplace page). The agent knows both when to pick it and what to do with the answer.

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