Skip to main content
Glama
SidneyBissoli

Banco Central do Brasil (BCB) — SGS MCP

by SidneyBissoli
OverviewSchemaSourceRelated ServersScoreDiscussions
TypeScript
Remote

bcb_cambio_moedas

Read-onlyIdempotent

Find the correct currency symbol or name before requesting exchange rates, filtering by term. Returns symbol, name, and type from the Brazilian Central Bank's published list.

Instructions

Lista as moedas com cotação publicada pelo Banco Central, com símbolo, nome e tipo, e aceita um termo para filtrar. Quando usar: para descobrir o símbolo correto antes de chamar bcb_cambio_cotacao (é a causa mais comum de cotação vazia). Quando NÃO usar: para valores de cotação. Retorna: termo, totalMoedas, moedas (simbolo, nome, tipo), disclaimer, qualificacaoParidade, urlConsulta e consultadoEm. Fonte: PTAX / Cotações e boletins de câmbio do Banco Central do Brasil, via Olinda OData. A resposta repassa literalmente o disclaimer de responsabilidade do BCB, em disclaimer. Cotações existem só em dia útil com fechamento de câmbio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termoNoFiltro por símbolo ou nome (ex.: 'EUR', 'libra'). Opcional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
termoNoTermo aplicado no filtro; nulo quando não foi informado
moedasYes
disclaimerYes
observacaoNo
provenanceYesBloco de proveniência (contrato v1.0): fonte, URL, competência, extração e licença
attributionYesURLs canônicas das fontes desta resposta (lista de atribuição)
totalMoedasYes
urlConsultaYes
consultadoEmYes
qualificacaoParidadeNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv1.9.2
    • addedOutput schema / properties / attribution
      Added value: +{
+  "description": "URLs canônicas das fontes desta resposta (lista de atribuição)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / provenance
      Added value: +{
+  "additionalProperties": false,
+  "description": "Bloco de proveniência (contrato v1.0): fonte, URL, competência, extração e licença",
+  "properties": {
+    "citation": {
+      "description": "Citação pronta para uso",
+      "type": "string"
+    },
+    "data_vintage": {
+      "description": "Competência do dado segundo a fonte; null quando a fonte não expõe",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "license": {
+      "description": "Regime legal do dado",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "retrieved_at": {
+      "description": "Instante REAL da extração na origem (ISO-8601, horário de Brasília). Resposta servida de cache mantém o instante do fetch ORIGINAL, que é a data de extração relevante.",
+      "type": "string"
+    },
+    "source": {
+      "description": "Fonte oficial do dado",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "URL canônica que reproduz a consulta",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "source_url",
+    "data_vintage",
+    "retrieved_at",
+    "citation",
+    "license"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "totalMoedas",
-  "moedas",
-  "disclaimer",
-  "urlConsulta",
-  "consultadoEm"
-]New value: +[
+  "totalMoedas",
+  "moedas",
+  "disclaimer",
+  "urlConsulta",
+  "consultadoEm",
+  "provenance",
+  "attribution"
+]
  2. Addedv1.6.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds context: the response includes a literal disclaimer from BCB, quotes only exist on business days, and the data source is PTAX via Olinda OData. These are meaningful behavioral details not present in annotations.

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 well-structured with clear sections (what, when, when-not, returns, source, caveats). Every sentence contributes useful information, and the essential use case is front-loaded.

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?

The description covers all necessary context: the tool's purpose, return fields, source, usage caveats, and relationship to sibling tools. It is complete for a simple, single-parameter, read-only tool.

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?

The single parameter 'termo' is fully described in the schema (100% coverage), and the description only restates that it filters without adding new semantic meaning. The baseline of 3 applies as the schema carries the burden.

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 lists currencies with quotes from the Central Bank, including symbol, name, and type, and accepts a filter term. It distinguishes itself from the sibling bcb_cambio_cotacao by explicitly positioning it as a precursor to that tool, eliminating ambiguity.

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

Usage Guidelines5/5

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

The description explicitly states when to use ('para descobrir o símbolo correto antes de chamar bcb_cambio_cotacao') and when not to use ('para valores de cotação'), naming the alternative tool. This provides direct, actionable guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SidneyBissoli/bcb-br-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server