Skip to main content
Glama

capacidades

Query petroleum-product storage capacity in thousands of m³ by company, installation, product, tank, or scope, with optional totals and airport-storage records.

Instructions

Capacidad de almacenamiento (miles de m3) por compañía, instalación y producto.

Fuente: PDF «Características de las instalaciones de almacenamiento» de la CNMC. producto = «TOTAL» es el total de la instalación. id_tanque es nulo cuando la instalación del PDF no tiene ficha en el portal. ambito: «almacenamiento» o «aeroportuaria». Una cifra nula significa que el PDF lista el producto sin desglose.

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

Input Schema

NameRequiredDescriptionDefault
ambitoNo
limiteNo
companiaNo
productoNo
id_tanqueNo
instalacionNo
solo_totalesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/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 usefully discloses the source PDF and the meaning of null values (product listed without breakdown) and null id_tanque, but says nothing about the limit/pagination behavior, whether results are capped at 300 by default, or whether output is a read-only listing — gaps that matter for a data query with 7 params.

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 definition is front-loaded with the core statement, then the source, then the caveats, with no filler. Line breaks make the parameter notes scannable. Some notes (e.g., the source attribution) are less actionable than others but still short.

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 no explanation, and the definition covers the trickiest data quirks (nulls, «TOTAL»). However, for a 7-parameter query tool with zero annotation and zero schema-description coverage, half the parameters and the default limit behavior are undocumented, leaving it only minimally sufficient.

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 coverage is 0%, so the description must compensate and it only does so partly: producto (with the special «TOTAL» value), id_tanque (null when no ficha exists) and ambito (with its two values «almacenamiento»/«aeroportuaria») are explained. The remaining parameters — limite, compania, instalacion, solo_totales — receive no meaning at all, and even ambito's allowed values are not framed as an enum-bound choice.

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 opening line names the resource precisely (storage capacity in thousands of m3) and its three grouping dimensions (company, installation, product), which lets an agent tell it apart from price or installation-listing siblings. There is no explicit verb or named alternative, but the data-retrieval purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description never says when to use this tool versus ver_instalacion, listar_instalaciones, or buscar_precios, nor does it state any exclusion or prerequisite. Usage can only be inferred from the parameter semantics, leaving the agent to guess at routing.

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