Skip to main content
Glama

Better Llama — Chile data

Series del Banco Central de Chile (BDE): dólar, TPM, IMACEC, PIB, desempleo

get_chile_central_bank_series
Read-onlyIdempotent

Consulta series estadísticas oficiales del Banco Central de Chile (BDE): dólar observado, euro, UF, UTM, tasa de política monetaria, IPC, IMACEC, PIB, desempleo, tipo de cambio real o cualquier código de serie, por rango de fechas o solo el último dato. Con operation=search busca códigos de series en el catálogo. / Official Central Bank of Chile statistical series.

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_central_bank_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoTexto a buscar / Search text — Solo operation=search. Todas las palabras deben aparecer en el título (español o inglés) o el código; no distingue tildes ni mayúsculas. Ej.: «imacec desestacionalizado».
lastDateNoHasta / To — AAAA-MM-DD. Por defecto: hoy (hora de Chile).
maxItemsNoMáximo de resultados a devolver (1-1000). Por defecto 100.
firstDateNoDesde / From — AAAA-MM-DD. Por defecto: 31 días antes de lastDate.
frequencyNoFrecuencia (búsqueda) / Frequency (search) — Solo operation=search.MONTHLY
operationNoOperación / Operation — series = observaciones de una o más series; search = buscar series en el catálogo por frecuencia y texto.series
seriesIdsNoCódigos de serie / Series codes — Códigos BDE (p. ej. F073.TCO.PRE.Z.D = dólar observado). Encuéntralos con operation=search o en el Buscador de Series de la BDE. Máximo 50. Si no indicas nada, se usa el dólar observado.
skipEmptyNoOmitir días sin dato / Skip empty — La BDE devuelve NaN en fines de semana y feriados. Por defecto se omiten.
indicatorsNoIndicadores frecuentes / Common indicators — Atajos con el código oficial ya resuelto. Se suman a seriesIds.
latestOnlyNoSolo el último valor / Latest value only — Entrega solo la observación más reciente con dato de cada serie (ideal para agentes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description confirms data comes from the official BDE catalog and that search mode exists, but adds no information on rate limits, error behavior, or response shape beyond what the schema states.

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 compact sentences with the resource and the covered series front-loaded, then the search-mode hint. The long indicator list duplicates the title and the 'indicators' enum, which is mild waste but also serves scanning by an agent, so it stays efficient overall.

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 10-parameter tool with two distinct operations and no output schema, the description covers both modes, the date-range vs latest-value choice, and how to obtain series codes. Annotations handle safety, so the remaining gap is only the return structure, which is not strictly required.

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 every parameter, including the F073.TCO.PRE.Z.D example, the 50-series cap, and the dólar observado fallback. The description only restates that search finds codes and that indicators/date ranges are accepted, adding little meaning beyond the structured fields — baseline 3.

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?

States a specific verb+resource ('Consulta series estadísticas oficiales del Banco Central de Chile (BDE)') and enumerates the concrete series covered (dólar observado, euro, UF, TPM, IPC, IMACEC, PIB, desempleo), plus the two operating modes ('series' vs 'operation=search'). Nothing about this reads like the earthquake, electricity, or stock-exchange siblings.

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?

Explicitly tells the agent to use 'operation=search' to resolve series codes in the catalog before querying, which is the key usage decision for this tool. It does not name an alternative sibling tool or state when a different tool (e.g. get_chile_financial_indicators) would be the better pick, so it falls short of a 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