brasil-mcp-essentials

Official

Overview Schema Source Related Servers Discussions Admin

lookup_cotacao_brl

Query Brazilian Central Bank PTAX rates for BRL conversion: get current or historical exchange rates for USD, EUR, GBP, JPY, ARS, CHF, CAD, and AUD.

Instructions

Consulta cotação PTAX BRL via Banco Central. Moedas: USD, EUR, GBP, JPY, ARS, CHF, CAD, AUD. data_cotacao opcional (default hoje). Cacheado 1h pra recente, 1 ano pra histórico.

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": {
      "moeda": "<moeda>"
    },
    "name": "lookup_cotacao_brl"
  }
}

Input Schema

Name	Required	Description	Default
`moeda`	Yes
`data_cotacao`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 30, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses caching behavior (1h for recent, 1 year for historical) and default date, but does not mention rate limits, authentication, or error handling. This is adequate but not comprehensive.

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?

Two concise sentences, each adding value: query action, currency list, optional date, caching policy. No wasted words, front-loaded with purpose.

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?

Given the tool's simplicity and the presence of an output schema, the description covers essential aspects: what it does, supported parameters with defaults, and caching behavior. No critical gaps remain.

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 0%, but the description explains 'moeda' by listing supported currencies and clarifies 'data_cotacao' as optional with default today. This adds significant meaning beyond the raw schema fields.

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 description clearly states it queries PTAX BRL exchange rates via the Central Bank, lists supported currencies, and specifies optional date parameter. This distinguishes it from sibling tools that focus on document validation or other lookups.

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 description provides context for when to use the tool (currency quote lookup) but lacks explicit when-not-to-use or alternative guidance. However, sibling tools are sufficiently different to avoid confusion.

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