Skip to main content
Glama

ipea_buscar

Read-onlyIdempotent

Search Ipeadata series by name text, original source, or theme to get the code needed for data retrieval. Call with no arguments to list available sources and themes.

Instructions

Procura séries no Ipeadata por texto no nome, com filtro por fonte original e tema; devolve o código para ipea_serie. Sem argumentos, lista fontes e temas.

Args: consulta: palavras do nome, todas obrigatórias; sem acento nem maiúscula. fonte: trecho da sigla ou do nome da fonte original ("ANP", "Receita", "Caged"). tema: nome ou código do tema. base: "macro" (padrão), "regional", "social" ou "todas". incluir_inativas: inclui séries descontinuadas. limite: até 100 resultados.

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": "ipea_buscar"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNomacro
temaNo
fonteNo
limiteNo
consultaNo
incluir_inativasNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/openWorld, so the description's job is to add operational detail — and it does: the zero-argument discovery mode, the 100-result cap, and that incluir_inativas surfaces discontinued series. It does not describe result shape or ranking of matches, which is a minor gap given no output schema.

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 the purpose and handoff, then a tight per-argument block with no filler. The opening sentence is dense (three clauses joined by semicolons) but every element is load-bearing; nothing is padded or repeated.

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?

For a six-parameter, no-output-schema search tool, the definition covers purpose, all parameters, the no-argument discovery mode, and pagination limits — enough to invoke correctly on the first try. What it omits is how results are ordered or how loosely matching behaves when multiple words are supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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: consulta requires all words, unaccented and lowercase; fonte takes an acronym or name fragment with concrete examples ('ANP', 'Receita', 'Caged'); tema accepts name or code; base supplies the enum values absent from the schema; limite and incluir_inativas are both explained. The only detail left thin is the limite default relationship to the schema's 25.

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 ('Procura séries no Ipeadata'), the search axis (text matching on the series name), the filters available, and the downstream relationship ('devolve o código para ipea_serie'). Naming ipea_serie as the consumer makes it distinguishable from sibling search tools without opening any schema.

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

Usage Guidelines4/5

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

Gives clear usage context: call with a text query to get codes, or call with no arguments to list available sources and themes for discovery. It does not explicitly exclude alternatives among the many other '*_buscar' siblings, but the Ipeadata scope plus the ipea_serie handoff makes intended use unambiguous.

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