Skip to main content
Glama

buscar_indicadores

Read-onlyIdempotent

Search Brazil’s curated official-data catalog by keyword, theme, or source to find indicator IDs for retrieving series, comparing indicators, or building panels.

Instructions

Localiza indicadores no catálogo curado de dados oficiais do Brasil.

Comece por aqui para descobrir o id a usar em obter_serie, comparar_series e painel. Sem argumentos, devolve os temas disponíveis e quantos indicadores cada um tem.

Args: consulta: palavras-chave, ex.: "selic", "ipca serviços", "dívida bruta". tema: restringe a um tema (ex.: inflacao, fiscal, credito). fonte: restringe a uma fonte (ex.: BCB, IBGE, Tesouro, IPEA). limite: máximo de resultados (padrão 15).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_indicadores"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaNo
fonteNo
limiteNo
consultaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.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 the safety profile is covered. The description adds genuinely useful behavior beyond them: the no-argument call returns the theme inventory with per-theme counts, and the default limit of 15 is stated inline. It does not say how matches are ranked (exact vs. substring, accent handling) or whether results are truncated/sorted, which matters for a search tool.

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 routing guidance, then no-arg behavior, then a compact Args block — a sensible order for an agent reading top-down. The Args section duplicates content that ideally lives in the schema, but given the 0% coverage it earns its place; no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and four undocumented schema parameters, the description does the heavy lifting: purpose, routing to downstream tools, no-arg return shape, and per-parameter meaning are all present. It stops short of describing the shape of a returned indicator record (id, name, theme, source), which is what the agent ultimately needs before calling obter_serie.

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 does so: each of the four parameters gets an explanation plus concrete examples ('selic', 'inflacao', 'BCB'). The only gap is that `limite` says 'máximo de resultados (padrão 15)' without stating ordering or truncation behavior, so the agent cannot predict which items get cut.

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?

States a specific verb and resource ('Localiza indicadores no catálogo curado de dados oficiais do Brasil') and immediately positions itself relative to siblings by naming obter_serie, comparar_series and painel as the consumers of the id it returns. An agent can distinguish discovery from retrieval without opening a 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?

'Comece por aqui para descobrir o `id` a usar em obter_serie, comparar_series e painel' explicitly tells the agent when to reach for this tool and which tools it feeds. It also documents the zero-argument mode ('devolve os temas disponíveis e quantos indicadores cada um tem'), giving a concrete fallback strategy.

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