Skip to main content
Glama
SidneyBissoli

IBGE Brasil MCP

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Notícias do IBGE

ibge_noticias
Read-onlyIdempotent

Search and list published IBGE news and press releases by keyword, type, date range, or featured status to find recent announcements about surveys or topics.

Instructions

Searches and lists already-published IBGE news articles and press releases.

Use this to find recent IBGE publications or announcements about a survey or topic — when an indicator was released, or news mentioning a term like "censo". Results are sorted newest-first; with no parameters it returns the 10 most recent items.

Parameters:

  • busca: free-text term to match (e.g. "PIB", "censo")

  • tipo: "release" (official publication of survey results) or "noticia" (general news); omit for both

  • de / ate: date range, format DD/MM/AAAA (e.g. de="01/01/2024", ate="31/12/2024")

  • destaque: true to return only featured items

  • quantidade: how many to return (default 10, max 100); pagina: page number to page through more

Each item returns: title, type (release/news), publication date, editoria (section), related products/surveys, a featured flag, a plain-text summary, and a link to the full article. The header reports the total count and current page.

Examples:

  • Latest 10 news: (no parameters)

  • Search census: busca="censo"

  • 2024 news: de="01/01/2024", ate="31/12/2024"

  • Releases only: tipo="release"

Use a different tool when:

  • Scheduled/upcoming release dates (not yet published) → ibge_calendario

Behavior: read-only and idempotent — a live GET against the public IBGE Notícias API. Returns a Markdown list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deNoData inicial no formato DD/MM/AAAA (ex: 01/01/2024)
ateNoData final no formato DD/MM/AAAA (ex: 31/12/2024)
tipoNoTipo de publicação: 'release' ou 'noticia'
buscaNoTermo para buscar nas notícias
paginaNoNúmero da página para paginação
destaqueNoFiltrar apenas notícias em destaque
quantidadeNoQuantidade de notícias a retornar (padrão: 10, máximo: 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
buscaNoTermo de busca aplicado, se houver
totalYesTotal de notícias encontradas na consulta
paginaYesPágina atual
noticiasYesLista de notícias retornadas
provenanceYesBloco de proveniência (contrato v1.0): fonte, URL, período, extração e licença
attributionYesURLs canônicas das fontes desta resposta (lista de atribuição)
totalPaginasYesNúmero total de páginas

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv4.0.0
    • removedOutput schema / properties / provenance / properties / data_vintage / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / provenance / properties / data_vintage / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / provenance / properties / license / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / provenance / properties / license / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Changed6 schema fields changedv3.3.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • 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, período, extração e licença",
+  "properties": {
+    "citation": {
+      "description": "Citação pronta para uso",
+      "type": "string"
+    },
+    "data_vintage": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Período de referência do dado segundo a fonte; null se a fonte não expõe"
+    },
+    "license": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Regime legal do dado"
+    },
+    "retrieved_at": {
+      "description": "Instante real da extração no upstream (ISO-8601, horário de Brasília)",
+      "type": "string"
+    },
+    "source": {
+      "description": "Fonte oficial do dado (API do IBGE consultada)",
+      "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: -[
-  "noticias",
-  "total",
-  "pagina",
-  "totalPaginas"
-]New value: +[
+  "noticias",
+  "total",
+  "pagina",
+  "totalPaginas",
+  "provenance",
+  "attribution"
+]
  4. Changed3 schema fields changedv3.0.0
    • changedInput schema / properties / ate / description
      Previous value: -"Data final no formato MM-DD-AAAA (ex: 12-31-2024)"New value: +"Data final no formato DD/MM/AAAA (ex: 31/12/2024)"
    • changedInput schema / properties / de / description
      Previous value: -"Data inicial no formato MM-DD-AAAA (ex: 01-01-2024)"New value: +"Data inicial no formato DD/MM/AAAA (ex: 01/01/2024)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "busca": {
+      "description": "Termo de busca aplicado, se houver",
+      "type": "string"
+    },
+    "noticias": {
+      "description": "Lista de notícias retornadas",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "dataPublicacao": {
+            "description": "Data de publicação (formato original da API)",
+            "type": "string"
+          },
+          "destaque": {
+            "description": "Indica se a publicação está em destaque",
+            "type": "boolean"
+          },
+          "editorias": {
+            "description": "Editoria(s) associada(s) à publicação",
+            "type": "string"
+          },
+          "introducao": {
+            "description": "Introdução/resumo da publicação (texto limpo)",
+            "type": "string"
+          },
+          "link": {
+            "description": "URL para a publicação completa",
+            "type": "string"
+          },
+          "produtos": {
+            "description": "Produtos do IBGE relacionados à publicação",
+            "type": "string"
+          },
+          "tipo": {
+            "description": "Tipo de publicação (ex: 'Release' ou 'Notícia')",
+            "type": "string"
+          },
+          "titulo": {
+            "description": "Título da notícia ou release",
+            "type": "string"
+          }
+        },
+        "required": [
+          "titulo",
+          "tipo",
+          "dataPublicacao",
+          "link"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagina": {
+      "description": "Página atual",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total de notícias encontradas na consulta",
+      "type": "number"
+    },
+    "totalPaginas": {
+      "description": "Número total de páginas",
+      "type": "number"
+    }
+  },
+  "required": [
+    "noticias",
+    "total",
+    "pagina",
+    "totalPaginas"
+  ],
+  "type": "object"
+}
  5. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds real behavior: newest-first sorting, default 10 with no params, max 100, pagination via pagina, and a live GET returning Markdown. It slightly restates 'read-only and idempotent' already in annotations, but the added operational detail is substantive.

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?

Front-loaded with purpose, then parameters, examples, and routing in clearly delimited sections. Slightly long with some redundancy (return-field list overlaps the output schema), but every section is scannable and earns its place.

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?

Complete for a zero-required-param search tool: coverage of all 7 params, default/pagination behavior, enum meaning, invocation examples, and sibling routing. The output schema exists, yet the description still conveniently summarizes returned fields without it being necessary.

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 100%, so baseline is 3, but the description genuinely extends meaning: it clarifies that tipo='release' is an official survey publication vs 'noticia' general news and that omitting returns both, and adds the DD/MM/AAAA format with examples beyond the raw schema.

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?

Specific verb+resource: 'Searches and lists already-published IBGE news articles and press releases.' It also distinguishes itself from the sibling ibge_calendario by scoping to already-published content, so an agent can tell them apart without opening either schema.

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?

Explicitly states when to use it ('find recent IBGE publications or announcements... when an indicator was released') and names the alternative with the disambiguating condition: scheduled/upcoming releases route to ibge_calendario. Includes concrete invocation examples.

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

Deploy Server

Other Tools