brasil-macro

copom

Read-onlyIdempotent

Retrieve Brazilian Central Bank Selic rate decisions, latest meeting dates, next meeting date, and statement or minutes text; supports selecting meetings and paging long documents.

Instructions

Decisões do Copom sobre a Selic, com comunicados e atas.

Sem documento, devolve as últimas reuniões (data, meta decidida, variação em p.p.) e a data da próxima. Com documento, devolve o texto do comunicado ou da ata.

Args: ultimas: reuniões listadas, da mais recente para trás. documento: "comunicado" ou "ata". reuniao: número da reunião; padrão: a mais recente disponível. max_caracteres: tamanho do trecho de texto devolvido. a_partir_de: posição inicial, para continuar a leitura de um documento longo.

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

Input Schema

Name	Required	Description	Default
`reuniao`	No
`ultimas`	No
`documento`	No
`a_partir_de`	No
`max_caracteres`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With annotations already declaring readOnly, openWorld, and idempotent, the description adds the important behavioral split: list mode returns meeting dates, decided target, variation, and next meeting date, while document mode returns text by chunk. It also explains pagination via `a_partir_de` and `max_caracteres`, though it does not discuss error or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then a focused mode explanation, then a compact args list. There is little repetition and no filler; each sentence or arg line supports calling the tool correctly.

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 five-parameter, two-mode tool without an output schema, the description supplies the return shape for both modes and explains how to continue reading a long document. Minor defaults are visible in the schema, so no essential behavior is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning, and it does for all five: `ultimas` bounds the list, `documento` accepts `comunicado` or `ata`, `reuniao` defaults to the latest available, and `max_caracteres` and `a_partir_de` define chunked reading. It adds critical semantics absent from the schema, especially the allowed `documento` values.

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?

The opening sentence names a precise resource, Copom decisions on the Selic, and the document types it returns. The second paragraph distinguishes list mode from document-text mode by parameter, so the agent can select the tool 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?

It states exactly how the two operating modes are selected: without `documento` it returns recent meetings, and with `documento` it returns statement or minutes text. It does not name when to prefer sibling tools, but the context is clear and no exclusions are implied.

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