Skip to main content
Glama
SidneyBissoli

IBGE Brasil MCP

by SidneyBissoli
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

ibge_sidra_tabelas

Read-onlyIdempotent

Search for SIDRA tables by name or survey filter to obtain the table code for querying IBGE data.

Instructions

Lists and searches available SIDRA tables.

Features:

  • List all SIDRA tables (aggregates)

  • Search by table name

  • Filter by survey (Census, PNAD, GDP, etc.)

  • Shows code and name of each table

SIDRA contains data from various surveys:

  • Demographic Census

  • PNAD Contínua (employment, income)

  • National Accounts (GDP)

  • Industrial Survey

  • Agricultural Survey

Examples:

  • List tables: (no parameters)

  • Search population tables: busca="população"

  • Census tables: pesquisa="censo"

This is step 1 of the SIDRA workflow: find a table code → ibge_sidra_metadados (structure) → ibge_sidra (query). For common data, a wrapper is usually easier: ibge_censo, ibge_indicadores, ibge_comparar, ibge_cidades.

Behavior: read-only and idempotent — a live GET against the public IBGE SIDRA API. Returns a Markdown table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buscaNoTermo para buscar no nome das tabelas/agregados
pesquisaNoFiltrar por código ou nome da pesquisa (ex: 'censo', 'pnad', 'pib')
limiteNoNúmero máximo de resultados (padrão: 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabelasYesLista de tabelas SIDRA retornadas
totalYesTotal de tabelas que correspondem aos critérios
buscaNoTermo de busca aplicado, se houver
pesquisaNoFiltro de pesquisa aplicado, se houver

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool performs a live GET against the public IBGE SIDRA API and returns a Markdown table. No contradictions with annotations.

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?

Well-structured with features, examples, workflow, and behavior. Each section adds value, though the features list could be slightly more concise.

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?

Comprehensive for a listing tool: covers purpose, usage, integration with other tools, and safety. With output schema present, return values need no explanation.

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 descriptions for all 3 parameters. The description adds English clarification but does not significantly enrich the parametric meaning beyond the 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?

The description clearly states it lists and searches SIDRA tables. It distinguishes itself from sibling tools by positioning as step 1 of a workflow and noting simpler wrappers for common data.

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 (first step of SIDRA workflow) and when not (common data wrappers like ibge_censo). Provides concrete examples for each parameter.

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/ibge-br-mcp'

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