Skip to main content
Glama

wintraits_comparar_fichas

Which version of my listing is better? Compares two listings of the same category. (¿Qué versión de mi ficha es mejor?)

Returns the diagnosis of each one (a and b), the difference in Wintraits Match Index points, a conclusion and the attributes read that differ between them. On the free plan both are shown in the free view.

Args: ficha_a: {"titulo", "precio_eur", "num_imagenes", "vinetas", "descripcion", "volumen_ml"} of the first. ficha_b: the same for the second (e.g. another version of the same listing). categoria: subcategory (see wintraits_categorias_disponibles; e.g. "serums"). pais: country code (see wintraits_categorias_disponibles; e.g. "ES"). lang: "es" (default) or "en" (attribute names in English).

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": {
      "ficha_a": "<ficha_a>",
      "ficha_b": "<ficha_b>"
    },
    "name": "wintraits_comparar_fichas"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
ficha_aYes
ficha_bYes
categoriaNoserums

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does fairly well: it enumerates the return payload (per-ficha diagnosis, Wintraits Match Index point delta, conclusion, differing attributes read), notes free-plan visibility, and states the beta is free and unlimited until 2027-01-31. It never explicitly states the operation is read-only/no-side-effect, which is the main remaining gap.

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 lead sentence and return summary are well front-loaded, but the definition is padded with bilingual duplication (the Spanish restatement of the title question and the free/beta notice repeated in two languages) and a Python-docstring 'Args:' block. Every fact is useful, but the presentation is roughly twice as long as needed.

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 correctly specifies what comes back (two diagnoses, index delta, conclusion, differing attributes). Inputs for a 5-parameter tool with nested free-form objects are substantially covered, though required inner keys and value types for ficha_a/ficha_b remain unstated.

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% and both ficha objects are free-form (additionalProperties: true, no documented inner keys), so the description is doing real work by naming the expected keys: titulo, precio_eur, num_imagenes, vinetas, descripcion, volumen_ml. It also explains categoria (subcategory, example 'serums'), pais (country code, example 'ES'), and lang ('es' default / 'en' for attribute names). It does not state which inner keys are required or their types, leaving some ambiguity.

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 opens with a concrete question and a specific verb+resource: it 'compares two listings of the same category' and returns which is better. The scope ('same category', 'ficha_a'/'ficha_b') is unambiguous. It does not explicitly contrast itself with siblings like wintraits_diagnosticar_producto or wintraits_indice_categoria, so it stops short of a 5.

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: use it when you want to know which of two versions of the same listing is better, and pass two variants of the same product. It routes the agent to wintraits_categorias_disponibles for valid categoria/pais values. It gives no explicit when-not guidance or named alternative for single-listing diagnosis.

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