Skip to main content
Glama

sidra_buscar_tabelas

Read-onlyIdempotent

Search IBGE SIDRA tables by keywords in table or survey names to find relevant official Brazilian statistics datasets.

Instructions

Procura tabelas do SIDRA (IBGE) por palavras-chave no nome da tabela ou da pesquisa.

Args: consulta: palavras-chave, ex.: "pib municípios", "rendimento domiciliar per capita". limite: máximo de resultados.

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": {
      "consulta": "<consulta>"
    },
    "name": "sidra_buscar_tabelas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
consultaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and determinism are covered structurally. The description contributes one genuine behavioral detail beyond them: matching happens against both table name and survey name. It says nothing about ranking, whether all keywords must match, or what the result entries contain.

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 purpose sentence is front-loaded and precise, and the whole definition is short. The 'Args:' block duplicates schema property names rather than adding structure, which costs a point but not much else.

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?

For a two-parameter search tool with no output schema, the definition covers inputs adequately but leaves the return shape unspecified — an agent cannot tell whether results include table IDs needed to chain into sidra_consulta. Given the tool is a discovery entry point, that connection is a meaningful omission.

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 description coverage is 0%, so the description carries the full burden and largely meets it: 'consulta' is defined as keywords with two concrete example queries, and 'limite' is identified as the maximum number of results. Missing are matching semantics (AND/OR across keywords) and whether limite has an upper bound, so the compensation is good but not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — searches SIDRA (IBGE) tables — and adds the matching scope: keywords in the table name or the survey ('pesquisa') name. An agent knows exactly what it returns conceptually. It does not distinguish itself from siblings like sidra_consulta or sidra_metadados, leaving the search-vs-fetch boundary to the agent's inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use statement and no named alternative. The description never says this is the discovery step that produces table identifiers for sidra_consulta, which is the most important routing fact for a catalog-lookup tool surrounded by data-fetching siblings.

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