Skip to main content
Glama

Better Llama — Chile data

Bolsa de Santiago: índices, precios y transacciones (trae tu clave)

get_santiago_stock_exchange_data
Read-onlyIdempotent

Consulta la API Brain Data de la Bolsa de Santiago: índices (IPSA y otros), instrumentos, precios, puntas, transacciones y resumen por acción, renta fija e intermediación financiera. Requiere tu propia API Key del Marketplace de la Bolsa (plan gratuito disponible) en el argumento apiKey o el encabezado X-Bolsa-Api-Key; los términos de la Bolsa no permiten que compartamos la nuestra. / Santiago Stock Exchange data (bring your own key).

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

Input Schema

NameRequiredDescriptionDefault
fechaNoFecha / Date — AAAA-MM-DD. Para índices (plan pagado), rf_benchmark y cg_garantia.
grupoNoGrupo (garantías) — Requerido en cg_garantia.
nemosNoNemotécnicos / Tickers — Ej. SQM-B, CHILE, COPEC. Requerido en transacciones, resumen_accion, variaciones_capital, precios y rf_transacciones; se consulta uno por uno.
apiKeyNoAPI Key de API Brain Data — Tu clave personal y gratuita del proveedor (https://api-braindata.bolsadesantiago.com). También puedes enviarla en un encabezado HTTP (ver la ficha de la herramienta). Se usa solo en esa solicitud; nunca se guarda ni se registra.
camaraNoCámara (compensación) — Requerida en cg_saldo_neto y cg_posicion_neta.
emisorNoEmisor (intermediación) — Requerido en if_transacciones e if_resumen_transacciones.
indiceNoÍndice — Código del índice (p. ej. IPSA) para índices del plan pagado, rf_indices y rf_benchmark.
familiaNoFamilia (renta fija) — Requerida en rf_instrumentos y rf_resumen_transacciones.
mercadoNoMercado — Mercado para instrumentos del plan pagado (p. ej. ACC, CFI).
periodoNoPeríodo — Período tal como lo define la API (resumen_accion, índices, resúmenes).
productNoProducto contratado / Product — Producto de tu suscripción. Por defecto: «free_trial» si la operación lo ofrece; si no, «mercado_valores» (renta variable, renta fija e intermediación financiera) o «compensacion».
maxItemsNoMáximo de resultados a devolver (1-500). Por defecto 50.
dividendoNoÍndice con dividendos — Solo índices del plan pagado.
operationNoOperación / Operation — Qué consultar. El plan gratuito incluye índices, instrumentos, puntas, transacciones, resumen de acción y variaciones de capital (renta variable, fin de día).indices
fechaDesdeNoDesde / From — AAAA-MM-DD. Por defecto: 7 días antes de «Hasta».
fechaHastaNoHasta / To — AAAA-MM-DD. Por defecto: hoy (Chile).
codigoCorredorNoCódigo de corredor — Opcional en compensación.
condicionLiquidacionNoCondición de liquidación — Opcional para puntas (plan pagado).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 real value beyond that by disclosing the bring-your-own-key auth model and why the provider's key cannot be shared, but it omits rate limits, plan-tier restrictions on specific operations, and any error behaviour for a tool spanning 18 operations.

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 front-loaded sentences plus a short English tagline; the data coverage comes first and the auth constraint second, with no filler. The bilingual restatement of "bring your own key" is mild redundancy but arguably serves discoverability.

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?

For an 18-parameter, multi-operation tool with no output schema, the description is thin: it does not indicate what a response looks like per operation, that nemos are queried one ticker at a time, or that several operations require paid products. The fully documented schema compensates substantially, but return shape and per-operation constraints remain undocumented anywhere.

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 100% schema description coverage and 18 well-annotated parameters, the baseline is a 3; the description nudges above it by explicitly naming the apiKey argument and header alternative and by grouping the callable data families that map onto the operation enum. It still adds no semantics for fecha, nemos, periodo, or the per-operation required parameters, leaving that entirely to the schema.

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 specific verb and resource ("Consulta la API Brain Data de la Bolsa de Santiago") and enumerates the asset coverage: índices, instrumentos, precios, puntas, transacciones, resumen por acción, renta fija and intermediación financiera. It is unambiguous about the domain, though it never explicitly contrasts itself with neighbouring Chile data tools such as get_chile_financial_indicators.

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 states a hard prerequisite – you must supply your own Marketplace API Key via apiKey or the X-Bolsa-Api-Key header – and notes a free plan exists, which is genuine usage guidance. However, it gives no when-to-use versus when-to-use-a-sibling guidance and does not warn which operations fall outside the free tier, so the agent must discover that from the operation enum description.

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