Skip to main content
Glama

wintraits_scan_perfil

What do today's best sellers in this category have? Winning attributes of a Scan category, no listing needed. (¿Qué tienen hoy los más vendidos de esta categoría? Atributos ganadores, sin pegar ninguna ficha.)

Full Scan profile: every trait that sets today's best sellers apart from the rest, with the share of each group that has it (pct_mas_vendidos, pct_resto), its tipo (producto = what the product is or offers, the part that also works outside Amazon; presentacion = how it is told online; tienda = depends on who sells), whether it counts in the Wintraits Scan Index, the medians of images, bullets, text length and price (cifras), the index bands and the link to its history. Use it to design or choose a product, brief a manufacturer, set price and format, or write a listing for Amazon, an own shop or another marketplace. To score a specific listing, use wintraits_chequeo_rapido. Exploratory snapshot, not validated with an exam: correlation, not causation.

Args: categoria: Scan category id (see wintraits_categorias_disponibles, solo_scan; e.g. "hidratantes"). pais: country code (e.g. "ES", "FR", "DE", "IT"). 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_scan_perfil"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so well: it discloses the returned fields (pct_mas_vendidos, pct_resto, tipo, index membership, cifras medians, index bands, history link), the epistemic caveat 'exploratory snapshot, not validated… correlation, not causation', and the cost/quota condition 'free and unlimited during the beta'.

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?

Front-loaded with the core purpose and the return shape, then caveats, then args, then cost — a sensible order. It's somewhat long and the bilingual duplication ('no listing needed' / 'sin pegar ninguna ficha', the repeated free-beta line) adds length without new information.

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 has to describe the return payload, and it does in detail down to field names and what each trait type means. Combined with the limitation caveat and the cost note, an agent has everything needed to call and interpret this tool.

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 carry the parameters and it does: categoria is tied to wintraits_categorias_disponibles with `solo_scan` and an example ('hidratantes'), pais lists sample codes (ES, FR, DE, IT), and lang is documented with its default 'es' and the 'en' alternative.

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 names a specific resource and scope: the winning attributes of a whole Scan category, explicitly 'no listing needed'. The opening line and the 'Full Scan profile' sentence together make it distinguishable from wintraits_chequeo_rapido, which it names as the per-listing scorer.

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 concrete when-to-use contexts (design or choose a product, brief a manufacturer, set price and format, write a listing for Amazon/own shop/other marketplace) and routes the agent to wintraits_chequeo_rapido for scoring a specific listing. What's missing is an explicit when-not to use it, e.g. against wintraits_diagnosticar_producto or wintraits_panorama_categoria.

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