Skip to main content
Glama

Andes Protocol - Chilean issuers (CMF)

Chilean company sales to the State

cmf_public_contracts
Read-onlyIdempotent

Use this to see what a Chilean company sells to the State: awards and tenders won in Mercado Público (ChileCompra), number of public buyers, period, awarded value in CLP and in USD at the latest CMF dollar, top buyers, top categories (UNSPSC) and procurement methods (direct vs competitive). Pass rut. Works for any supplier, registered with the CMF or not. Only Andes joins this with the CMF registry. 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_public_contracts"
  }
}

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.2/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, it discloses access conditions (anonymous agents allowed but rate-limited; a free AndesPass key raises the limit) and the currency-conversion basis (latest CMF dollar). It does not describe result volume, pagination or coverage lag, which would round it out.

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 the purpose, then scope, differentiator and access in a compact sequence. The long field enumeration is dense but each item answers 'what will I get', so it earns its place; minor trimming of the list would be possible.

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?

Single-parameter read tool with an output schema, so return values need no explanation. The description covers data source, scope, currency treatment, authentication tiers and the cross-registry claim — everything needed to decide and call correctly.

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% and the schema already gives the RUT format and example, so the description's 'Pass rut' adds no new meaning. Baseline 3 applies when the schema carries the parameter documentation.

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 (see what a Chilean company sells to the State) and enumerates the returned content: awards and tenders in Mercado Público, buyer counts, awarded value in CLP and USD, top buyers, UNSPSC categories and procurement methods. That detail distinguishes it cleanly from cmf_entity_profile, cmf_financials and the other registry siblings.

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?

'Works for any supplier, registered with the CMF or not' and 'Only Andes joins this with the CMF registry' tell the agent the applicable scope and the differentiator versus registry tools. There is no explicit when-not or named alternative, but the domain is unambiguous enough that routing is not left 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