Skip to main content
Glama

wintraits_indice_categoria

How many launches win in this category? How long does a new serum take to take off on Amazon Spain? (¿Cuántos lanzamientos triunfan en esta categoría? ¿Cuánto tarda en despegar un sérum nuevo?)

Wintraits Success Ratio: of every 100, how many win and how many fail, median days to take off, overall and by quarter. Only groups with 30 launches or more. cita has the public URL and the date of the data to cite it.

Args: categoria: subcategory (see wintraits_categorias_disponibles; e.g. "serums"). pais: country code (see wintraits_categorias_disponibles; 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

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

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaNoserums

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 reasonably well: it discloses the 30-launch minimum-grouping rule (data suppression behaviour), the presence of a `cita` field carrying a public URL plus data date for citation, and that access is free and unlimited until 2027-01-31. It does not describe the response shape in detail or say whether missing/thin categories produce an error or an empty result.

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?

Content is front-loaded with the motivating question before the metric definition, and the Args block is easy to scan. The main waste is the full bilingual duplication of both the framing questions and the beta notice, which roughly doubles length without adding information for an agent that reads either language.

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, so the description must describe returns, and it covers the essentials: win/fail counts per 100, median days to take off, quarterly breakdown, and the `cita` citation field. Given three simple optional string parameters, this is close to sufficient; only the handling of thin categories and the exact response structure remain unstated.

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 coverage is 0%, so the description must compensate, and it does: categoria is identified as a subcategory with the example value "serums", pais as a country code with example "ES", and lang as "es" (default) or "en" — including which are defaults, which the bare schema only shows in `default` fields. It additionally points to wintraits_categorias_disponibles as the authoritative source of valid values.

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 names a concrete metric set (win/fail ratio per 100 launches, median days to take off, overall and by quarter) rather than restating the name, and the framing questions make the analytical question it answers obvious. It stops short of explicitly contrasting itself with neighbours such as wintraits_panorama_categoria, so an agent must infer the boundary.

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?

Usage context is clear ('How many launches win in this category? How long does a new serum take to take off on Amazon Spain?') and the eligibility constraint — only groups with 30+ launches — tells the agent when the tool will not return results. It also routes the agent to wintraits_categorias_disponibles for valid categoria/pais values, though it gives no explicit when-not-to-use case.

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