Skip to main content
Glama

buscar_precios

Search current prices with filters by service text, category, operator, product, or installation type. Returns each price with its source and document reference; use it to locate pricing data.

Instructions

Precios vigentes con filtros. No agrupa: para comparar usa comparar_servicio.

Cada precio dice su fuente: «html» (la página del detalle) o «pdf» (una tarifa en PDF a la que remite el detalle; documentos es el PDF y pagina_pdf la página). Una línea «html» con tipo_precio «pdf» es solo el puntero al documento; resuelto_en dice en qué tablas están sus datos. Un precio de PDF que vale para varios detalles sale una sola vez, con aplica_a (nº de detalles e instalaciones); con detallar_aplicacion=true incluye la lista.

categoria: categoria_servicio exacta (p. ej. «almacenamiento»). texto: parte de la etiqueta o subetiqueta del servicio. tipo_precio puede ser numerico, regla (p. ej. «según contrato»), texto o pdf (remite a un documento; valor nulo).

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

Input Schema

NameRequiredDescriptionDefault
textoNo
limiteNo
operadorNo
productoNo
categoriaNo
comunidadNo
solo_numericosNo
tipo_instalacionNo
detallar_aplicacionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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 behavioral burden. It discloses meaningful domain behavior about provenance (`fuente` html vs pdf), pointer rows and `resuelto_en`, and de-duplication with `aplica_a`. It says nothing about permissions, rate limits, default `limite` behavior, or pagination, so it is partial rather than complete.

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 most valuable routing information is front-loaded in the first sentence. After that the text drifts into output-field semantics (`fuente`, `documentos`, `pagina_pdf`, `resuelto_en`) that overlap with the existing output schema, so a portion of the length does not earn its place given what the agent already receives.

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?

For a nine-parameter filtered search tool with no annotations and a rich output schema, the description supplies the domain model needed to interpret results correctly (provenance, aggregation, applicability). The main shortfall is that the majority of input filters remain unexplained, which the output schema cannot cover.

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 nine parameters, so the description must compensate. It explains only three: `categoria` (exact categoria_servicio), `texto` (part of label or sublabel) and `detallar_aplicacion` (include the list). `limite`, `operador`, `producto`, `comunidad`, `solo_numericos` and `tipo_instalacion` are left entirely undefined, and some prose describes returned fields (tipo_precio, fuente) rather than inputs.

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?

"Precios vigentes con filtros" names the resource and scope, and the follow-up sentence carves out a specific boundary: it does not group prices and directs comparisons to `comparar_servicio`. The verb is implicit and it does not distinguish itself from other price-related siblings, but the resource is unambiguous.

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?

One explicit when-not is given ("No agrupa: para comparar usa `comparar_servicio`"), which is genuinely useful routing. However, there is no guidance on when to use this instead of other price-oriented siblings, nor on filter combinations, defaults, or the purpose of most of the nine filters.

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