Skip to main content
Glama

wintraits_buscar_categoria

Find the category code from words: "air fryer", "juegos de mesa", "vitamin C serum", "puzzles". (Busca el código de una categoría a partir de palabras, en español o en inglés.)

Call it before any other tool when you do not know the exact categoria: never guess codes. Returns up to 15 matches, best first, with categoria and pais (pass them as they come to the other tools), the name, nivel ("match": every tool; "scan": wintraits_scan_perfil, wintraits_ranking, wintraits_chequeo_rapido, wintraits_chequeo_asin) and the link. With no match, use wintraits_categorias_disponibles.

Args: texto: what the user sells or wants to sell, in Spanish or English. pais: preferred country code ("ES", "FR", "DE", "IT"); matches in that country come first. 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": {
      "texto": "<texto>"
    },
    "name": "wintraits_buscar_categoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNo
textoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/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 burden and does so: it discloses result cardinality (up to 15), ordering (best first), returned fields (categoria, pais, name, nivel, link), the meaning of nivel and which downstream tools each level unlocks, and the licensing/rate context (free and unlimited during beta until 2027-01-31).

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 action and examples, then usage rule, then return shape, then args, then licensing. Dense but each section is useful; the bilingual duplication of the description and beta note is slightly redundant but not wasteful.

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?

No output schema exists, yet the description fully specifies the return shape and semantics of nivel, covers all three parameters, and gives a fallback path. Nothing an agent needs to invoke and interpret this tool is missing.

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: texto is defined as what the user sells or wants to sell in Spanish or English, pais as a preferred country code with the effect that matches in that country sort first, and lang as es (default) or en. This adds meaning beyond the bare typed properties.

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?

States a specific verb and resource ('Find the category code from words') with concrete example queries, and distinguishes itself from wintraits_categorias_disponibles as the fallback when no match exists. An agent can identify this as the code-lookup tool without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says to 'Call it before any other tool when you do not know the exact categoria: never guess codes,' which is a clear when-to-use rule and an anti-pattern to avoid. It also names the alternative (wintraits_categorias_disponibles) for the no-match 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