Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

Chilean issuer CMF sanctions

cmf_sanctions
Read-onlyIdempotent

Use this to check whether the CMF sanctioned a Chilean securities issuer in the securities market (2002 onward). Pass rut. The CMF searches its sanctions register by name, not by RUT, so results come with the name searched and a match_note: a resolution may concern a similarly named company or several companies at once; open document_url (the resolution) before attributing it. An empty list means none found under that name. 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_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutYesThe issuer's RUT (Chilean tax id), e.g. 61.808.000-5.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description still adds non-obvious behavior: the register searches by name rather than RUT, results carry a match_note flagging similarly named or multiple companies, document_url must be opened before attributing a resolution, and an empty list means no match.

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 caveats, then access/rate-limit note; every sentence is actionable and nothing is repeated from schema or annotations. It is slightly dense in a single paragraph and the terse 'Pass rut.' could be folded into the preceding sentence, but there is no 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?

For a one-parameter lookup with an output schema, this is complete: the description supplies the caveats the output schema cannot convey as prose (name-based matching, match_note interpretation, empty-list semantics) plus authentication and rate-limit behavior, leaving nothing an agent needs before calling.

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 coverage is 100% with one documented parameter, so the baseline is already met. The description still adds real meaning by explaining that the RUT is resolved to a name for lookup and that mismatches are possible, which tells the agent why a returned name may differ from the queried identifier.

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?

Specific verb, resource, jurisdiction and time coverage: 'check whether the CMF sanctioned a Chilean securities issuer in the securities market (2002 onward)'. That scope is clearly distinct from siblings such as cmf_entity_profile, cmf_financials or cmf_material_events, so an agent can route without opening the 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?

The opening 'Use this to check whether...' sets the intended task and 'Pass rut' tells the agent the single required input. It gives clear context for use but never names an alternative tool or an exclusion (e.g., when to prefer cmf_entity_profile for general issuer background), so it falls short of explicit 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