Skip to main content
Glama

sgs_buscar

Read-onlyIdempotent

Search SGS series in the Banco Central open-data catalog by keywords to find the series code, title, and frequency needed for data retrieval.

Instructions

Procura séries do SGS no catálogo de dados abertos do Banco Central, por palavras-chave.

Devolve código, título e periodicidade; use o código em sgs_serie. A busca cobre só as séries publicadas como dados abertos, não o SGS inteiro.

Args: consulta: palavras-chave, ex.: "inadimplência cartão de crédito". limite: máximo de resultados (até 100).

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
consultaYes

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 safety and repeatability are covered. The description adds useful behavior: the shape of the return (código, título, periodicidade) and the coverage boundary of the index. It does not discuss pagination or whether limite truncates silently, though that is a minor gap given the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences front-load the purpose, the return and the handoff, followed by a compact Args block. Nothing is redundant — the example and the 100-result cap both add information not present elsewhere.

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?

For a two-parameter lookup tool with no output schema, the description supplies the essential missing pieces: what is returned, the scope limitation of the catalog, and the next call to make. There is no material gap an agent would need to guess at.

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 coverage is 0%, so the description must carry the parameters, and it does: consulta is explained with a concrete keyword example, and limite is given a real cap (up to 100) that the schema does not state, adding genuine meaning beyond the default of 20. Coverage is not exhaustive on matching behavior (e.g. accent/substring handling), which keeps it at 4.

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 (search SGS series in the Banco Central open data catalog) plus the mechanism (keyword search) and the return fields. It also names the downstream sibling sgs_serie, so an agent can distinguish lookup from retrieval without opening the 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?

Explicitly tells the agent to take the returned code and use it in sgs_serie, and warns that the search only covers series published as open data, not the whole SGS. No explicit exclusion against other search siblings, but the workflow context is clear.

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