Skip to main content
Glama

Better Llama — Chile data

Precios de bencina, diésel y gas por estación en Chile (CNE)

find_chile_fuel_prices
Read-onlyIdempotent

Encuentra precios actuales de combustibles (gasolina 93/95/97, diésel, kerosene, GLP, GNC) por estación de servicio en Chile, filtrando por región, comuna, marca o cercanía a una coordenada (radio en km), ordenados por precio o distancia. También lista estaciones con dirección y servicios. / Current fuel prices per gas station in Chile.

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

Input Schema

NameRequiredDescriptionDefault
fuelsNoCombustibles / Fuels — Vacío = todos.
brandsNoMarcas / Brands — Copec, Shell, Aramco, Petrobras, Abastible… Vacío = todas.
outputNoSalida / Output — precios = una fila por estación y combustible (ideal para «¿dónde está más barata?»); estaciones = una fila por estación con todos sus precios.precios
sortByNoOrden / Sort — Por defecto: distancia si das un punto; si no, precio (precios) o sin orden (estaciones).
comunasNoComunas / Communes — Nombre (Providencia, Ñuñoa…) o código. Vacío = todas.
regionsNoRegiones / Regions — Código CNE (13) o nombre (Valparaíso, Biobío, RM…). Sin tildes ni mayúsculas. Vacío = todo Chile.
latitudeNoLatitud / Latitude — Opcional: punto de referencia para calcular distancia (p. ej. -33.4263).
maxItemsNoMáximo de resultados a devolver (1-200). Por defecto 20.
radiusKmNoRadio (km) / Radius (km) — Opcional: solo estaciones dentro de este radio del punto.
longitudeNoLongitud / Longitude — Opcional (p. ej. -70.6170).
serviceTypeNoAtención / Service — Filtra por precio asistido o de autoservicio.todos
includeMaintenanceNoIncluir estaciones en mantenimiento — Por defecto se omiten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say how current the 'precios actuales' are, where the data comes from, whether results are paginated or truncated, or what happens with maintenance-status stations — despite a schema flag for that behavior.

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?

Two sentences, front-loaded with the core purpose followed by the secondary 'también lista estaciones' capability, and the trailing English gloss is brief. The bilingual repetition adds minor redundancy but no confusion, and nothing drags.

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 12-parameter, all-optional filter tool with no output schema, the description covers the domain, the filter axes and the two result shapes (prices per station vs. station listing with address and services). Gaps remain around result pagination/truncation and data freshness, but the essentials for selecting and calling it are present.

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 100% and each parameter already carries bilingual descriptions, defaults and enums, so the baseline is 3. The prose only restates the filter set (fuels, region, comuna, brand, radius in km, ordering by price or distance) without adding syntax, format or edge-case meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Encuentra precios actuales de combustibles ... por estación de servicio en Chile') and enumerates the fuel types and filter dimensions, so an agent knows exactly what data domain this covers. No sibling tool operates on fuel prices, and the scoping to Chile/CNE-style per-station data makes the boundary obvious.

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?

Usage is implied through the filter list (region, comuna, brand, proximity radius) and the mention that it also lists stations with address and services, but there is no explicit when-to-use/when-not statement or named alternative. With no competing sibling in this domain, the omission is low-risk but still a gap versus a 4 or 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources