Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

Chilean issuer IFRS figures

cmf_financials
Read-onlyIdempotent

Use this for the key figures of a Chilean issuer's IFRS financial statements as filed with the CMF: revenue, operating income, net income, total assets, liabilities, equity, cash, financial debt and cash flows, for the latest filed quarter (or period, e.g. 2026-06) with the comparative columns, in full currency units, plus headline figures in USD. Consolidated when available. include_all_lines=true adds every published line. Labels stay as the CMF's IFRS taxonomy labels (label_es). Access: open to anonymous agents (rate-limited); a free AndesPass key raises the limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rut": "<rut>"
    },
    "name": "cmf_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutYesThe issuer's RUT (Chilean tax id), e.g. 61.808.000-5.
periodNoQuarter end as yyyy-mm (e.g. 2026-06); omit for the latest filed.
include_all_linesNotrue adds every line of every statement as published (long).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the bar is lower, yet the description adds real behavioral context: anonymous access is rate-limited and a free AndesPass key raises the limit, values are in full currency units with USD headline figures, consolidation is applied when available, and labels remain in the CMF IFRS taxonomy (label_es). It also flags that include_all_lines=true produces a long response, which is a practical cost signal.

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 purpose and scope are front-loaded in the opening clause, and each subsequent clause carries distinct information (default period, currency units, USD headline, consolidation, labels, access tiers). It is dense and runs long for a single paragraph, but there is no redundant restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still covers units, consolidation policy and label language, and it resolves the only real access question (anonymous rate limits vs. AndesPass). Nothing an agent needs in order to call this correctly is missing for a three-parameter read-only tool.

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?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents rut, period and include_all_lines. The description still adds value by framing period as "latest filed" by default with a concrete 2026-06 example and by warning that include_all_lines=true returns the long, full published line set rather than just headline figures.

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 resource (a Chilean issuer's IFRS financial statements as filed with the CMF) and enumerates the exact figures returned (revenue, operating income, net income, assets, liabilities, equity, cash, financial debt, cash flows). It is unambiguous what the tool retrieves, though it never explicitly contrasts itself with siblings like cmf_entity_profile or cmf_material_events, which the distinct data domain makes largely unnecessary.

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?

"Use this for the key figures..." gives a clear positive trigger, and "for the latest filed quarter (or period, e.g. 2026-06)" plus "omit for the latest filed" clarifies the period-selection context. It offers no explicit when-not guidance or named alternatives, which keeps it at 4 rather than 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