Skip to main content
Glama

comparar_servicio

Compare prices for a service category across installations and operators, keeping only comparable groups by category, included service indicators, and unit to avoid mixing figures.

Instructions

Compara el precio de una categoría de servicio entre instalaciones y operadores.

Solo son comparables los precios de un mismo grupo: misma categoría, mismos indicadores de lo que incluye el servicio (transporte, almacenamiento, expedición, puesta a bordo) y misma unidad. Si salen varios grupos, la respuesta lo avisa: no mezcles sus cifras. Incluye los precios de las tarifas en PDF (fuente «pdf», con su documento y página; solo tienen año, no fecha). Un precio de PDF común a varios detalles aparece una vez, con aplica_a (detallar_aplicacion=true añade la lista de detalles). Los servicios sin precio numérico se listan aparte con resuelto_en.

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": "comparar_servicio"
  }
}

Input Schema

NameRequiredDescriptionDefault
operadorNo
productoNo
categoriaYes
comunidadNo
tipo_instalacionNo
detallar_aplicacionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does it well: it discloses grouping/warning behavior, that PDFs are included with document/page and year-only dates, the deduplication via `aplica_a`, and that unpriced services surface separately via `resuelto_en`. What is missing is any statement about read-only nature or result ordering/volume, but the operational semantics are unusually well surfaced.

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 purpose, then progressively narrower constraints and edge cases in short sentences. Dense but every sentence carries information about real behavior; only minor tightening is possible.

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?

An output schema exists, so return values need not be documented, and the description still explains key response behaviors (group warning, `resuelto_en`, `aplica_a`). The gap is on the input side: four filter parameters are left unexplained, which for a 6-parameter comparison tool leaves an agent guessing how to narrow the comparison.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description must compensate. It explains `detallar_aplicacion` and implicitly `categoria`, but `operador`, `producto`, `comunidad` and `tipo_instalacion` receive no meaning at all, leaving four parameters undocumented in both schema and prose.

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?

States a specific verb and resource ('compara el precio de una categoría de servicio') and its scope ('entre instalaciones y operadores'), which is precise enough for an agent to grasp the operation. It does not name or contrast itself with the closest sibling (buscar_precios, precios_origen_destino), 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 Guidelines3/5

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

Usage is strong on comparability rules — same category, same inclusion indicators, same unit — and warns not to mix figures across groups. However, it never says when to prefer this tool over the sibling price tools, so the when-to-use guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.