Skip to main content
Glama

historial_precio

Retrieves every historical price version for a tank installation, including valid and expired records, observation dates, CNMC validity dates, and current-status flags.

Instructions

Todas las versiones de los precios de un detalle, vigentes o no.

Cada fila dice entre qué fotos se vio (primera_vez_visto … ultima_vez_visto) y la fecha de vigencia que publica la CNMC (fecha_precio). vigente indica si sigue en la última foto. etiqueta/subetiqueta: parte del nombre del servicio.

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": {
      "id_tanque_instalacion": "<id_tanque_instalacion>"
    },
    "name": "historial_precio"
  }
}

Input Schema

NameRequiredDescriptionDefault
etiquetaNo
subetiquetaNo
id_tanque_instalacionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/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 useful work by declaring that non-current versions are included, that each row is bounded by first/last seen photo, and that 'vigente' means still present in the latest snapshot. It still omits ordering, result size, and pagination for what is likely an unbounded history list.

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 scope, then a compact glossary of the returned columns. The quoting and line wrapping are slightly noisy but no sentence is filler.

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 the column-by-column explanation is a bonus rather than a requirement, and the description covers it well. What is missing is guidance on the required installation-tank id and on how much history comes back, which matters for a three-parameter history endpoint.

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

Parameters3/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. It explains etiqueta/subetiqueta as 'part of the service name', which adds real meaning, but leaves the only required parameter, id_tanque_instalacion, entirely unexplained and gives no hint about when to pass the optional filters.

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 resource and scope: all versions of the prices of a 'detalle', current or not. The verb is implicit ('return list') but the resource and scope are unambiguous. It does not differentiate from search-oriented siblings such as buscar_precios, which keeps it below 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?

The phrase 'vigentes o no' implies the tool's niche — retrieving full history rather than a current snapshot — which lets an agent infer when to prefer it over a price-search tool. However, it never names an alternative or states an explicit when-not-to-use condition.

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