Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

Chilean issuer profile

cmf_entity_profile
Read-onlyIdempotent

Use this to know who a Chilean securities issuer is: legal name, status, stock ticker, address, board of directors (role in English, date of the latest election: re-elected directors show it too, see board_dates_note), executives, the 12 largest shareholders with their ownership and the controlling shareholder when one holds more than half, plus a brief on its sales to the Chilean State. Pass rut (e.g. 61.808.000-5; dots, dash and check digit optional). Read from the CMF registry, cached a day, with a source_url per section. Personal ID numbers are left out. 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_entity_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutYesThe company's RUT (Chilean tax id), e.g. 61.808.000-5; dots, dash and check digit optional.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description still adds real operational context the annotations cannot convey: one-day caching, a per-section source_url, omission of personal ID numbers, and anonymous access with rate limits raised by an AndesPass key.

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 and the returned-field inventory, followed by short operational sentences on input, caching, privacy and access. The opening sentence is long and carries a dense list, but every clause is informative and nothing reads as filler.

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?

Covers identification, input format, data provenance, caching freshness, privacy constraints and auth/rate-limit behavior. With an output schema present, return values need no further explanation, so nothing an agent needs in order to call this correctly is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage, including the '61.808.000-5; dots, dash and check digit optional' note. The description restates that example almost verbatim, so it adds no meaning beyond the structured field — 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?

Opens with a specific verb and resource — 'Use this to know who a Chilean securities issuer is' — and enumerates exactly what the profile contains (legal name, status, ticker, board, executives, shareholders, state sales). That content list makes it clearly distinct from cmf_financials and cmf_list_issuers without needing to name them.

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?

Gives clear context for when to reach for it ('to know who a Chilean securities issuer is') plus the required input and access conditions. It stops short of naming an alternative tool or stating when not to use it, so it lands at a solid 4 rather than 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