Skip to main content
Glama

wintraits_scan_historia

How has this category changed? History of the Wintraits Scan Index of a Scan category. (¿Cómo ha cambiado esta categoría?)

For each update: middle half (25-75 %) and median of the Wintraits Scan Index of best sellers and of the rest. If the best sellers' band rises, a listing needs to look more like them to be among them.

Args: categoria: Scan category id (see wintraits_categorias_disponibles). 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_scan_historia"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 mostly meets it: it discloses the returned statistics per update (25–75% band and median, split between best sellers and the rest) and states the cost profile (free and unlimited during beta until 2027-01-31). It does not state the time window or granularity of "each update", nor ordering of results.

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 purpose and return structure are front-loaded and the interpretation sentence earns its place. However, the length is inflated by full bilingual duplication of the parenthetical question and the beta/rate-limit note, which repeats the same fact twice without adding information.

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

Completeness3/5

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

No output schema and no annotations, so the description must cover both purpose and returns; it describes the returned statistics adequately. The significant remaining gap for a history tool is the period covered and the granularity of updates, which an agent needs to interpret the result correctly.

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 does for all three parameters: categoria is defined as a Scan category id with a pointer to wintraits_categorias_disponibles, pais as a country code with the "ES" example, and lang as "es" (default) or "en", supplying values the schema does not enumerate. It omits only that pais also defaults to "ES".

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?

"History of the Wintraits Scan Index of a Scan category" gives a specific resource (the index) plus a temporal dimension that distinguishes it from a point-in-time index tool. The framing question "How has this category changed?" reinforces that this is a trend/history view. It stops short of naming which sibling to use for the current snapshot.

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 by the opening question and by the interpretation note ("If the best sellers' band rises, a listing needs to look more like them"), which tells the agent what question this answers. It also routes to wintraits_categorias_disponibles for valid category ids. There is no explicit when-not guidance or comparison against the sibling that returns the current index.

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