Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

List Chilean securities issuers

cmf_list_issuers
Read-onlyIdempotent

Use this to find a Chilean company registered with the CMF (the financial regulator) when you do not know its RUT, or to see the whole universe of active securities issuers (about 340: listed companies, bond issuers, pension fund managers, utilities). Pass query with part of the legal name (e.g. 'aguas', 'sonda') or of the RUT; leave it empty to list all. Returns RUT and legal name, with the registry's source_url. Access: open to anonymous agents (rate-limited); a free AndesPass key raises the limit.

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": "cmf_list_issuers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum issuers returned (1 to 400).
queryNoPart of the legal name (e.g. 'aguas') or of the RUT; empty lists every issuer.

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?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-structured context: anonymous access, rate limiting, and that a free AndesPass key raises the limit. The stated return fields (RUT, legal name, source_url) are somewhat redundant given an output schema exists, which keeps this 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?

Four compact sentences, front-loaded with purpose and then usage, with the access/rate-limit note placed last where it belongs. Minor redundancy in repeating the returned fields and the query examples already present in structured data.

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?

Annotations cover safety, the output schema covers return values, and the schema covers both parameters. The description closes the remaining gaps an agent needs before calling: dataset size, access model, and rate limits.

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%, so both parameters are already documented in the schema, including the partial-name/partial-RUT semantics of query and the empty-lists-all behavior. The description restates those examples without adding new syntax, format, or edge-case guidance, so the baseline of 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?

States a specific verb and resource: find a Chilean company registered with the CMF, or enumerate the universe of active securities issuers. The parenthetical breakdown (listed companies, bond issuers, pension fund managers, utilities) and the ~340 count make the scope concrete enough to separate it from siblings like cmf_entity_profile or cmf_financials.

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 an explicit triggering condition: use it when you do not know the RUT, which implicitly routes RUT-known lookups elsewhere. It does not name or exclude a specific alternative tool or state when-not to use it, so it falls short of full when/when-not guidance.

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