Skip to main content
Glama

listar_operadores

Lists petroleum storage operators with their installation counts and details by type, including prior names, optionally filtering to only those with installations.

Instructions

Operadores (almacenistas) con su nº de instalaciones y detalles, por tipo.

Una instalación con dos titulares (p. ej. Exolum Corporation y Exolum Aviation en un aeropuerto) cuenta para los dos. nombres_anteriores son los nombres con que el portal ha publicado antes ese mismo código.

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

Input Schema

NameRequiredDescriptionDefault
solo_con_instalacionesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does not say the operation is a read, nor mention rate limits or auth. It does however disclose two genuinely non-obvious data behaviors: that a facility with two owners (Exolum Corporation and Exolum Aviation at an airport) is counted for both, and what `nombres_anteriores` means. That is real value the schema cannot provide.

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?

Three short sentences, front-loaded with the resource and its contents, followed by two clarifications that each carry information. The airport example is slightly verbose but illustrates a counting rule that would otherwise be ambiguous, so it earns its place.

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 explained, and the counting rule and `nombres_anteriores` are covered. What is missing for a one-parameter listing tool is any explanation of that parameter and any routing guidance relative to the installation-oriented siblings.

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?

The single parameter `solo_con_instalaciones` has 0% schema description coverage and is never mentioned in the description. The one behavior an agent must know before calling — whether setting it to false includes operators with zero installations — is left entirely unexplained, so the description does not compensate for the coverage gap.

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 states a specific resource and output shape: operators ('almacenistas') with their number of installations and details, grouped 'por tipo'. An agent knows what the tool returns. The gaps are that 'por tipo' is never defined (type of what?) and there is no contrast with the sibling listar_instalaciones, so the distinction must be inferred.

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?

There is no when-to-use guidance at all, and no mention of listar_instalaciones or ver_instalacion as alternatives, even though an agent choosing between listing operators and listing installations would need exactly that. The grouping phrase 'por tipo' implies a use case but never states one.

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