Skip to main content
Glama

wintraits_ranking

Which best sellers have the most complete listings? TOP 10 of the Wintraits Scan Index of a category. (¿Qué más vendidos tienen la ficha más completa? Ranking del Índice Wintraits Scan.)

Among today's best sellers, the 10 with the highest Wintraits Scan Index (out of sample) and the index traits each listing has (rasgos), with the best sellers' middle half (franja_mas_vendidos). Brand, title and Amazon link only for listings with an index of 60 or more. Use it as examples of how the best sellers present the winning traits; the number is not comparable across categories and is not a sales probability.

Args: categoria: Scan category id (see wintraits_buscar_categoria; e.g. "freidoras"). pais: country code (e.g. "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": {
      "categoria": "<categoria>"
    },
    "name": "wintraits_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 well: it discloses the out-of-sample nature of the index, the conditional field exposure (brand, title and Amazon link only for index >= 60), the extra `franja_mas_vendidos` band, and the beta access terms (free and unlimited until 2027-01-31). Remaining gaps are minor, e.g. ordering/tie behavior within the top 10.

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 content is front-loaded and every English sentence conveys real information, but the full Spanish mirror of every sentence roughly doubles length, and the beta/free notice is repeated bilingually. Useful for human readers, somewhat wasteful for an agent parsing the definition.

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, yet the description explains what comes back: the index value, the listing traits (`rasgos`), the best-seller middle band (`franja_mas_vendidos`), and which fields are gated by the 60+ threshold. For a fixed-size top-10 tool with three parameters, an agent has everything needed to call and interpret it.

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 does: `categoria` is defined as a scan category id with a cross-reference to wintraits_buscar_categoria and an example ("freidoras"), `pais` is a country code with example ("ES"), and `lang` is restricted to "es"/"en" with a stated default. This adds value the bare schema does not carry, including the allowed lang values that the schema does not enforce.

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 states a concrete resource and operation: the top 10 best sellers ranked by the Wintraits Scan Index within a category, plus the traits each listing has. It is specific enough to distinguish from index/attribute siblings, but it never names an alternative tool to contrast with, leaving differentiation implicit.

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

Usage Guidelines4/5

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

It gives explicit interpretive guidance: 'Use it as examples of how the best sellers present the winning traits', and warns the number is not comparable across categories and is not a sales probability. That is strong context, though it stops short of saying when to prefer this over siblings such as the category index or winning-attributes tools.

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