Skip to main content
Glama

wintraits_opciones_concepto

Valid attributes and values for wintraits_evaluar_concepto and for the optional atributos of wintraits_diagnosticar_producto in a category. instrucciones_extraccion says exactly how to read them from a listing.

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". The keys and values to send back are always the Spanish ids.

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

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
categoriaNoserums

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose quota behavior — free and unlimited during the beta until 2027-01-31 — and points to an instrucciones_extraccion field explaining how to read the values, which is genuine context beyond structured data. It stops short of describing the overall return shape or confirming the operation is a pure read with no side effects.

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?

The layout is well front-loaded: purpose first, then a structured Args block, then the quota note. The one waste is the beta notice being given twice, once in English and once in Spanish, which adds nothing for an agent. Otherwise every sentence carries 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?

For a three-parameter reference lookup with no output schema and no annotations, the definition covers inputs well but only gestures at the output ('valid attributes and values', plus the mention of instrucciones_extraccion). Since there is no output schema, the description should say more about the payload structure — e.g., whether attributes map to value lists. Adequate but not complete.

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 coverage is 0%, so the description must compensate, and it does: categoria is described as a subcategory with the example 'serums', pais as a country code with example 'ES', and lang as 'es' default or 'en' with the important constraint that the keys and values sent back are always Spanish ids. That language rule is meaning the schema cannot convey. Minor gap: no format constraints such as case sensitivity or ISO code format.

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 identifies the resource precisely — the set of valid attributes and their allowed values for a category — and names the two sibling tools that consume it (wintraits_evaluar_concepto and the atributos field of wintraits_diagnosticar_producto). An agent can distinguish it from the category-listing tool without opening the schema. The only weakness is that the verb is implicit; it never says outright 'returns' or 'lists'.

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?

It names the consumers, which implies this is a prerequisite lookup before evaluating a concept, and it routes the agent to wintraits_categorias_disponibles for valid categoria/pais values. However, it never states the sequencing explicitly ('call this first'), gives no when-not-to-use condition, and does not say whether the result can be reused across calls.

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