mcp-brasilapi

Overview Schema Source Related Servers Discussions Admin

cambio__consultar_cotacao

Retrieve the exchange rate of Brazilian Real (BRL) against a specified currency for a given date. Input currency code and date.

Instructions

Consulta a cotação do Real em relação a uma moeda em uma data.

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>",
      "data": "<data>"
    },
    "name": "cambio__consultar_cotacao"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Data no formato AAAA-MM-DD (ex.: "2024-01-15").
`moeda`	Yes	Símbolo da moeda (ex.: "USD", "EUR").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the query purpose, but does not disclose whether it is read-only, authorization requirements, rate limits, or what happens if data is unavailable. Critical behavioral traits are missing.

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 a single sentence of 13 words, extremely concise, and front-loaded with the core purpose. No superfluous information.

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?

Given the simplicity (2 params, output schema exists), the description is minimally adequate. It tells what the tool does but lacks usage guidance and behavioral context. The output schema helps but does not excuse missing behavioral transparency.

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% with both 'moeda' and 'data' described. The description adds minimal value beyond the schema, merely restating the parameter concepts. Baseline 3 is appropriate as schema already documents the parameters adequately.

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 the tool queries the exchange rate of BRL against a specified currency on a given date. It uses a specific verb ('Consulta') and resource (cotação do Real), and is distinct from siblings like 'cambio__listar_moedas' which lists available currencies.

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

Usage Guidelines3/5

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

The description provides context for what the tool does, but does not specify when to use it versus alternatives (e.g., 'cambio__listar_moedas' for listing currencies). No explicit guidance on prerequisites or when not to use.

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