Skip to main content
Glama

dados_abertos_buscar

Read-onlyIdempotent

Search official BNDES or ANEEL open-data portals for datasets, returning titles, descriptions, pages, and CSV/XLSX/API resources to open or download.

Instructions

Busca conjuntos de dados nos portais de dados abertos oficiais: portal 'bndes' (operações, desembolsos e financiamentos do BNDES) ou 'aneel' (energia elétrica: geração, tarifas, outorgas). Devolve o título, a descrição, a página e os recursos (CSV, XLSX, API) de cada conjunto, para o usuário abrir ou baixar.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
portalYes
consultaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=true), and the description adds genuinely new behavioral context: it discloses the return payload (title, description, page, resource links in CSV/XLSX/API) even though no output schema exists. It does not mention rate limits, pagination behavior, or whether results are ranked by relevance.

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?

Two sentences, front-loaded with the verb and resource, then the portal taxonomy, then the return shape. Minor waste in the parenthetical enumerations, but nothing is filler and the ordering is logical for an agent scanning quickly.

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 three-parameter read-only search tool with no output schema, the description covers the essentials: what is searched, where, and what comes back. The gaps are the undocumented 'limite' and 'consulta' semantics, which leave the agent guessing about result caps and query formatting.

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 description coverage is 0%, so the description must carry the load. It does explain the most important parameter, 'portal', by giving the two accepted values and what data each serves, but it never defines 'consulta' (search syntax? free text? accents?) and says nothing about 'limite', which has a default of 10 but no stated maximum or effect.

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?

The description states a specific verb and resource ('Busca conjuntos de dados') and names the two target portals with the subject matter each covers (BNDES financing operations, ANEEL electricity generation/tariffs/grants). That distinguishes it from series-oriented siblings such as sgs_buscar or ipea_serie, though it never explicitly contrasts itself with any named sibling tool.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this tool is for discovering dataset catalogs (to then open or download) instead of fetching series values. There is no explicit when-not-to-use statement, no mention of what to do if the portal is not bndes/aneel, and no guidance on how many results are typically useful.

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