Skip to main content
Glama

wintraits_hallazgos

What has been discovered and confirmed about winning products? Validated findings. (¿Qué se ha descubierto y comprobado sobre los productos que triunfan?)

Each finding was discovered with some launches and then repeated in at least two 8-week periods with launches the system had not seen. Includes statement, lift with 95 % interval, products, period, attribute family, stability (1-3) and cita. On the free plan you see the 3 most stable per category; for the rest, the statement without figures (bloqueados). Agency plan: also those under observation, marked preliminar. Without a category: all of them.

Args: categoria: subcategory (see wintraits_categorias_disponibles; empty = all). pais: country code (empty = all). lang: "es" (default) or "en" (attribute names in English; statements stay in Spanish for now).

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

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNo
categoriaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 per-finding payload (statement, lift with 95% interval, products, period, attribute family, stability 1-3, cita) and important access-tier behavior — free plan sees only the 3 most stable per category while the rest return statements without figures as 'bloqueados', and the agency plan also exposes 'preliminar' items. It omits anything about response size, ordering, or latency, and never explains what 'cita' actually contains.

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 payload information is front-loaded, but the description is effectively doubled by a parallel Spanish translation of nearly every sentence, including the beta notice, which adds length without adding information for most agents. The opening is phrased as a question and then restated, costing a sentence.

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?

With no output schema and no annotations, this description supplies the return shape, the tier gating, and all parameter semantics, which is close to what an agent needs. The remaining gaps are the unexplained 'cita' field, the absence of an example category/country value, and no sense of result volume.

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%, yet the Args section documents all three parameters: categoria (with the pointer to wintraits_categorias_disponibles and empty = all), pais (country code, empty = all), and lang (default 'es', 'en' switches attribute names while statements stay Spanish). This fully compensates for the empty schema, though it lacks format examples for the country code and calls 'categoria' a 'subcategory', which is mildly ambiguous.

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 specific resource with a clear scope: confirmed/validated findings about winning products, including how they were validated (discovered on some launches, then repeated in at least two 8-week periods with unseen launches). It does not differentiate itself from the sibling 'wintraits_evidencia', which by name sounds closely related, so an agent cannot fully disambiguate without inspecting both.

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

Usage Guidelines3/5

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

Usage is implied rather than prescribed: it tells the agent to look up subcategories via 'wintraits_categorias_disponibles' and that an empty category returns all, but it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives such as wintraits_evidencia or wintraits_atributos_ganadores. The plan-based behavior hints at who should call it, but no exclusions are stated.

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