Skip to main content
Glama

Better Llama — Chile data

Mercado eléctrico de Chile: costos marginales, generación y demanda (Coordinador Eléctrico)

get_chile_electricity_market
Read-onlyIdempotent

Consulta datos públicos del Coordinador Eléctrico Nacional (SIP): costo marginal en línea y real por barra, generación real y diaria por central, demanda neta y real, catálogo de centrales y líneas, limitaciones de transmisión, servicios complementarios y energía no suministrada. Usa "filter" para acotar por barra o central. / Chile electricity market data (marginal costs, generation, demand).

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

Input Schema

NameRequiredDescriptionDefault
filterNoFiltro de texto / Text filter — Opcional. Texto (sin mayúsculas/minúsculas) que debe aparecer en el nombre: barra en costos marginales (p. ej. «crucero 220», «QUILLOTA»), central o tecnología en generación, instalación o empresa en limitaciones. Se aplica después de descargar cada página (la API no filtra por barra).
datasetNoConjunto de datos / Dataset — Qué consultar en el Sistema de Información Pública (SIP).costo_marginal_online
endDateNoHasta / End date — AAAA-MM-DD (incluido). Por defecto igual a startDate. Máximo 31 días por llamada.
maxItemsNoMáximo de resultados a devolver (1-500). Por defecto 50.
startDateNoDesde / Start date — AAAA-MM-DD. Por defecto: ayer (hora de Chile). No aplica a los catálogos de centrales y líneas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that the source is the public SIP and identifies the dataset coverage, but says nothing about return shape, page-by-page downloading, the 31-day cap, or error behavior — those constraints live only in the schema.

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 source and a compact enumeration of datasets, then the filter hint. The bilingual Spanish/English restatement has some duplication, but the core content is dense and each clause carries dataset information rather than filler.

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 read-only, open-world data retrieval tool with no output schema and zero required parameters, the description supplies the source, the full dataset menu, and the filter mechanism. Return payload structure and pagination behavior are unstated, which is the main residual gap.

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%, so the schema already documents filter, dataset, dates, and maxItems thoroughly, including the post-download filtering caveat. The description's "use filter to narrow by bar or plant" repeats rather than extends the schema. Baseline 3 applies.

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 states a specific verb and resource (query public data from the Coordinador Eléctrico Nacional SIP) and enumerates the concrete data families: marginal cost online/real per bar, real and daily generation per plant, net and real demand, plant and line catalogs, transmission limits, ancillary services, and unserved energy. This is far more specific than any sibling Chile tool, which cover banking, seismic, financial, tenders, etc.

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?

It gives one practical hint — use "filter" to narrow by bar or plant — but never states when to pick it over a sibling or when it is not appropriate. The dataset list implies the intended uses, but no explicit when/when-not guidance is present.

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