Skip to main content
Glama

cmf_buscar_sanciones

Read-only

Search Chile's CMF official registry for sanction resolutions and penalty procedures by entity name, violation, or resolution number.

Instructions

Busca en el registro oficial de Resoluciones Sancionatorias y procedimientos de sanción aplicados por la CMF.

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": {
      "query": "<query>"
    },
    "name": "cmf_buscar_sanciones"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNombre de la entidad sancionada, infracción o número de resolución

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the purpose statement — no indication of coverage period, result format, or result volume for an open-world registry lookup.

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?

A single compact sentence with no filler, front-loading the verb and resource. It is appropriately sized, though it conveys only the minimum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only search, the description is minimally adequate, but with no output schema it could say a bit more about what the registry covers or what results look like. Nothing critical is missing, but the definition is thin given the breadth of sibling search tools.

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% for the single 'query' parameter, and its schema description already explains it accepts an entity name, infraction, or resolution number. The description adds nothing 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb ('Busca') and a specific resource ('registro oficial de Resoluciones Sancionatorias y procedimientos de sanción aplicados por la CMF'). However, it does not distinguish itself from related sanction-search siblings such as sma_search_sancionatorios or cgr_search_auditorias, so an agent must infer the CMF-specific scope from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. With many sibling search tools (sma, cgr, tdlc, sii), the absence of routing guidance is a noticeable gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools