Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

Chilean issuer material events

cmf_material_events
Read-onlyIdempotent

Use this to see what a Chilean securities issuer disclosed to the CMF as material events (hechos esenciales): dividends, shareholders' meetings, management changes, securities placements, mergers and more. Pass rut and optionally days (how far back, default 365, up to 1825). Each event has filed_at, the topic in English and as published (topic_es), the document number and document_url (the filing, PDF in Spanish). The topic is the issuer's own choice; 'Other' says nothing about the content, so open the document before concluding. 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_material_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutYesThe issuer's RUT (Chilean tax id), e.g. 61.808.000-5.
daysNoHow far back, in days (1 to 1825; default 365).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), it discloses access behavior not captured anywhere structured: anonymous access with rate limiting and a free AndesPass key raising the limit. It also flags where the underlying content lives (PDF in Spanish at document_url), which is real operational context. It says nothing about pagination or result caps, which keeps it from a 5.

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 purpose, then parameters, then the returned fields, then access notes — a sensible progression with no filler. It is on the longer side and the event-type enumeration is somewhat expendable, but every sentence carries usable information.

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?

With annotations covering safety and an output schema covering return values, the description still supplies the pieces an agent needs to act correctly: required identifier, lookback window, the caveat that topics are self-reported and vague, and authentication/rate-limit expectations. Nothing material is missing for a two-parameter read tool.

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 coverage is 100%, so both rut and days are already documented with example format, default and range. The description restates the same days semantics (default 365, up to 1825) without adding syntax or constraint detail beyond the schema, so the 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 — what a Chilean securities issuer disclosed to the CMF as material events — and enumerates the concrete event types (dividends, shareholders' meetings, management changes, placements, mergers). This makes it clearly distinguishable from sibling tools like cmf_financials or cmf_sanctions without opening any schema.

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?

It gives clear usage context: pass rut, optionally days, plus an explicit warning that the 'Other' topic is uninformative and the document must be opened before concluding. It does not, however, name any sibling tool or state when to prefer another endpoint (e.g. contracts vs sanctions), so routing is left partly to inference.

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