Skip to main content
Glama

reconsignaciones

Query Exolum PDF price matrices to find gasoline and diesel delivery reassignment prices between origin and destination facilities, along with ester consignment and origin-destination table data.

Instructions

Precios de las matrices de los PDF de Exolum entre dos instalaciones.

tipo «reconsignacion» (por defecto): cambiar la instalación de entrega de gasolinas y gasóleos, de la instalación ORIGEN a la de DESTINO. tipo «consignacion_ester»: consignación del éster metílico para mezcla en línea. tipo «origen_destino»: las tablas origen-destino tal como vienen en el PDF (para el día a día usa precios_origen_destino, que parte de la página web). origen/destino: parte del nombre («Huelva», «Rivabellosa»). Cada precio indica el PDF, la página y el año de la tabla. Estado «no_aplica» = «(*)».

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

Input Schema

NameRequiredDescriptionDefault
tipoNoreconsignacion
limiteNo
origenNo
destinoNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 burden. It does disclose useful semantics the agent could not infer: each price records its source PDF, page and table year, and status `no_aplica` corresponds to "(*)" in the PDF. It never states that the operation is read-only, how installation names are matched (substring?), or fallback behavior when a name matches nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the resource and output meaning come first, then each `tipo` mode, then parameter semantics, then the `no_aplica` convention. Every sentence carries information an agent needs; the odd line-wrapping is cosmetic rather than wasteful.

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?

Return values needn't be restated given the output schema, and the description usefully explains the per-price metadata (PDF, page, year) and the `no_aplica` marker. Gaps remain for a four-parameter tool: `limite` is unexplained, and the agent is not told whether partial-name matching is exact, case-sensitive, or ambiguous. Adequate but not complete.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well: it defines all three `tipo` values and their distinct semantics, and explains that `origen`/`destino` are substrings of installation names, with examples ("Huelva", "Rivabellosa"). This is meaning the bare schema cannot convey. The `limite` parameter (default 200) is never mentioned, so one of four params remains undocumented.

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 names a concrete resource and scope: price matrices extracted from Exolum PDFs between two installations, with the three `tipo` variants spelled out. It explicitly distinguishes the `origen_destino` mode from the sibling `precios_origen_destino` (web-page based), so an agent can route correctly. The retrieval verb is only implied ("Precios de las matrices de los PDF"), which keeps it just 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 Guidelines4/5

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

Clear when-to-use guidance for the key ambiguity: "para el día a día usa `precios_origen_destino`, que parte de la página web", plus a stated default for `tipo` ("reconsignacion"). No exclusions or prerequisites are given for the other siblings (`buscar_precios`, `consulta_sql`), and nothing is said about when the PDF-based data is unavailable.

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