Skip to main content
Glama

Better Llama — Chile data

UF, dólar, euro, UTM, IPC y reportes bancarios (CMF Chile)

get_chile_financial_indicators
Read-onlyIdempotent

Obtiene indicadores oficiales de la CMF Chile: UF, dólar observado, euro, UTM, IPC, TMC y TIP (valor vigente, por día, mes, año o rango), y reportes bancarios (balances, estados de resultados, perfil, adecuación de capital) por banco. JSON con fecha ISO y valor numérico. / Official Chilean financial indicators (UF, USD, EUR, UTM, CPI) and bank reports from CMF.

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

Input Schema

NameRequiredDescriptionDefault
dayNoDía / Day — 1-31. Solo UF, dólar y euro (period=date o inicio de un range por días).
yearNoAño / Year — AAAA. Obligatorio para period year/month/date/range y para reportes bancarios (salvo adecuación por regresión).
dayToNoDía hasta / Day to — Fin del rango por días (dólar y euro).
monthNoMes / Month — 1-12. Obligatorio para period=month/date y para reportes bancarios.
periodNoPeríodo (indicadores) / Period — Solo indicadores. current = valor vigente; year / month / date = un año, un mes o un día; range = entre year(/month[/day]) y yearTo(/monthTo[/dayTo]). El rango por días (dias_i / dias_f) está documentado y verificado para dólar y euro. UF, UTM, IPC, TMC y TIP usan rango por meses o años.current
sourceNoRecurso / Resource — Indicadores: uf, dolar, euro, utm, ipc, tmc, tip. Reportes bancarios: balances, resultados, perfil, accionistas, integrantes, adecuacion. La Tasa TAB UF 360 está suspendida por la CMF (no se ofrece).uf
yearToNoAño hasta / Year to — Fin del rango (period=range).
monthToNoMes hasta / Month to — Fin del rango por meses o por días.
maxItemsNoMáximo de resultados a devolver (1-500). Por defecto 50.
accountCodeNoCódigo de cuenta / Account code — Código contable CMF. El plan de cuentas vigente usa códigos de 9 dígitos (p. ej. 105000000 = Efectivo y depósitos en bancos; el 1000000 de la documentación de 2009 ya no devuelve datos). Si se omite, se entrega el estado completo del banco en ese mes (pueden ser cientos o más de mil líneas; usa maxItems).
listCatalogNoCatálogo / Catalog — Solo balances o resultados. instituciones = lista de bancos con datos en ese mes; cuentas = plan de cuentas del mes. Vacío = detalle (estado o cuenta).
institutionCodeNoCódigo de institución / Institution code — Código SBIF de 3 dígitos (001 = Banco de Chile, 012 = BancoEstado, 028 = BICE, 999 = sistema financiero). Obligatorio en perfil, accionistas, integrantes y adecuación. En balances/resultados, si se omite y no hay accountCode, se lista el catálogo de instituciones del mes.
regresionMonthsNoMeses de regresión / Regression months — Solo adecuacionResource=regresion_*. Entre 1 y 24. Por defecto 12.
adecuacionResourceNoRecurso de adecuación de capital / Capital adequacy resource — irs = patrimonio efectivo / activos ponderados por riesgo (%%); ire = capital básico / activos totales (%%); componentes = desglose; regresion_* = últimos N meses (el más reciente debería ser el último publicado; en una prueba de 2026 este endpoint devolvió series de 2020).irs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact with no output schema present: results come back as JSON with ISO dates and numeric values. It says nothing about response size for full bank statements, staleness of regression series, or the suspended TAB UF 360 rate — all of which 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?

The content is front-loaded in a single dense Spanish sentence followed by a short English gloss. The gloss is largely duplicative, which costs a little, but the overall size is tight for a tool covering this many resources.

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?

Given 14 parameters and two very different modes (indicator lookup vs. bank financial statements), the description gives a correct high-level picture and even states the return format, which matters with no output schema. It does not signal that the two modes require different parameters (institutionCode, accountCode, listCatalog) or that full statements can be very large, so an agent must read the schema to call it safely.

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% across 14 parameters, so the schema already carries the semantics and the baseline of 3 applies. The description loosely maps its indicator/report lists onto the `source` enum, but adds no syntax, defaults, or constraints beyond what the schema states.

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 verb ('Obtiene') and a well-defined resource set: official CMF Chile indicators (UF, dólar observado, euro, UTM, IPC, TMC, TIP) plus bank reports (balances, estados de resultados, perfil, adecuación de capital). Explicitly attributing the data to CMF helps separate it from the sibling get_chile_central_bank_series, but no sibling is named, so the differentiation is implicit rather than stated.

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?

There is no explicit when-to-use / when-not-to-use guidance or named alternative. Usage is only implied by the enumerated resource list and the mention of periods (valor vigente, por día, mes, año o rango), which an agent must infer from the schema to act on.

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