Banco Central do Brasil (BCB) — SGS MCP

Documento para Deep Research

fetch

Read-onlyIdempotent

Retrieve the full document for a valid id from search results, including title, text, url, and metadata, to cite Banco Central do Brasil time series data.

Instructions

Returns the full document for an id obtained from search, as { id, title, text, url, metadata }: text is the readable content (Markdown) and url the canonical public page to cite.

Companion of search in the OpenAI Deep Research contract, over the Banco Central do Brasil time series (SGS: interest rates, inflation, exchange rates, credit, fiscal and external sector — the curated catalog plus the open data portal index) catalog. Only ids returned by search are valid; an unknown id returns an error. The bcb_* tools remain the tools for data queries.

Behavior: read-only and idempotent — a live GET against the public source when the document needs it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Identificador de um documento devolvido por `search`

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Identificador único do documento no servidor; é o que `fetch` recebe
`url`	Yes	URL pública canônica do documento — a citação do ChatGPT depende dela
`text`	Yes	Conteúdo integral do documento, legível (Markdown)
`title`	Yes	Título legível do documento
`metadata`	No	Pares chave/valor adicionais sobre o documento (tipo, fonte, período…)
`provenance`	Yes	Um bloco por procedência que contribuiu com esta resposta (contrato v1.1; licenças nunca se fundem)
`attribution`	Yes	URLs canônicas das fontes desta resposta (lista de atribuição)

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.15.0Sep 27, 2026

changedOutput schema / properties / provenance / description

Previous value: -"Um bloco por procedência que contribuiu com esta resposta (contrato v1.0; licenças nunca se fundem)"New value: +"Um bloco por procedência que contribuiu com esta resposta (contrato v1.1; licenças nunca se fundem)"

changedOutput schema / properties / provenance / items / description

Previous value: -"Bloco de proveniência (contrato v1.0): fonte, URL, competência, extração e licença"New value: +"Bloco de proveniência (contrato v1.1): fonte, URL, competência, extração, diagnóstico de origem, citação e licença"

changedOutput schema / properties / provenance / items / properties / citation / description

Previous value: -"Citação pronta para uso"New value: +"Citação/atribuição pronta para uso"

changedOutput schema / properties / provenance / items / properties / data_vintage / description

Previous value: -"Competência do dado segundo a fonte; null quando a fonte não expõe"New value: +"Competência/vintage do dado segundo a fonte; null quando a fonte não expõe"

changedOutput schema / properties / provenance / items / properties / license / description

Previous value: -"Regime legal do dado"New value: +"Regime legal do dado (id SPDX quando há, senão o nome da licença)"

addedOutput schema / properties / provenance / items / properties / retrieval

Added value: +{
+  "description": "Diagnóstico de origem da chamada: como o dado foi obtido. Medição real do servidor; unstable=true pede ao agente que trate o dado como obtido com dificuldade; null quando o servidor não mede",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "description": "Diagnóstico de origem da chamada: como o dado foi obtido. Medição real do servidor; unstable=true pede ao agente que trate o dado como obtido com dificuldade",
+      "properties": {
+        "anomalies": {
+          "description": "Anomalias superadas até o sucesso, somadas por classe, em ordem fixa; [] se nenhuma",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "count": {
+                "description": "Ocorrências desta classe na chamada",
+                "minimum": 1,
+                "type": "integer"
+              },
+              "kind": {
+                "description": "Classe da anomalia (vocabulário fechado do contrato)",
+                "enum": [
+                  "timeout",
+                  "network",
+                  "http_4xx",
+                  "http_5xx",
+                  "rate_limited",
+                  "malformed_body"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "count"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attempts": {
+          "description": "Tentativas somadas, incluindo as repetidas (>= requests)",
+          "minimum": 1,
+          "type": "integer"
+        },
+        "requests": {
+          "description": "Idas distintas à origem que compõem esta resposta (fatias, páginas)",
+          "minimum": 1,
+          "type": "integer"
+        },
+        "unstable": {
+          "description": "true se houve repetição (attempts > requests) ou alguma anomalia",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requests",
+        "attempts",
+        "anomalies",
+        "unstable"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / provenance / items / properties / retrieved_at / description

Previous value: -"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."New value: +"Instante REAL da extração na origem (ISO-8601, fuso do servidor). Resposta servida de cache mantém o instante do fetch original, que é a data de extração relevante"

changedOutput schema / properties / provenance / items / properties / source_url / description

Previous value: -"URL canônica que reproduz a consulta"New value: +"URL canônica que reproduz a consulta na fonte"

changedOutput schema / properties / provenance / items / required

Previous value: -[
-  "source",
-  "source_url",
-  "data_vintage",
-  "retrieved_at",
-  "citation",
-  "license"
-]New value: +[
+  "source",
+  "source_url",
+  "data_vintage",
+  "retrieved_at",
+  "retrieval",
+  "citation",
+  "license"
+]

Addedv1.12.1Sep 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior; the description adds value by explaining the live GET behavior against the public source and the error condition for unknown ids. It also clarifies the output format, which is useful beyond the annotation metadata.

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?

The description is front-loaded with the core behavior and output shape, then adds context about the catalog and sibling tools. It is somewhat dense but each sentence contributes useful information, and the structure is logical: behavior, context, exclusions, and behavior note.

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 single-parameter read-only tool with rich annotations and an output schema, the description covers everything needed to invoke it correctly: where the id comes from, what the output contains, error behavior, and relationship to sibling tools. No critical gap remains.

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?

The schema already documents `id` as an identifier from `search` with 100% coverage, so the baseline is 3. The description adds meaningful behavioral semantics: only valid search-returned ids work and unknown ids error, which helps the agent understand the parameter's constraints beyond the schema text.

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 opens with a specific verb and resource: 'Returns the full document for an id obtained from `search`', and specifies the exact output shape. It also distinguishes itself from sibling tools by positioning itself as the companion of `search` and explicitly stating that `bcb_*` tools are for data queries.

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?

It gives clear usage context: use after `search`, only ids returned by `search` are valid, and unknown ids produce an error. It also provides an exclusion by directing data-query needs to the `bcb_*` tools, so an agent knows when not to call this tool.

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

Deploy Server