Skip to main content
Glama

sgs_serie

Read-onlyIdempotent

Fetch any Brazilian Central Bank SGS time series by its code, including date ranges, latest values, and transformations when the series is not in the catalog.

Instructions

Qualquer série do SGS (BCB) pelo código, quando não está no catálogo. Use sgs_buscar para achar códigos.

Args: codigo: número da série, ex.: 432 (meta Selic). inicio, fim, ultimos, transformacao: como em obter_serie.

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": {
      "codigo": "<codigo>"
    },
    "name": "sgs_serie"
  }
}

Input Schema

NameRequiredDescriptionDefault
fimNo
codigoYes
inicioNo
ultimosNo
transformacaoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotence are covered. The description adds useful context (examples of codes, where to get them) but says nothing about rate limits, what happens with an invalid code, date handling, or return shape — moderate added value over the structured fields.

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 core purpose and the routing rule, then a compact args block. No wasted prose; the only weak spot is that brevity here comes partly at the cost of parameter detail.

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 read-only lookup tool with five undocumented parameters and no output schema, the definition leaves real gaps: date format for inicio/fim, valid values for transformacao, and precedence between ultimos and the date range. The codigo example and the cross-reference partially fill in, but an agent would still be guessing.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters. The description only explains 'codigo' (with a concrete example, 432 = meta Selic) and delegates the other four to 'como em obter_serie', which forces the agent to consult a different tool's docs rather than compensating for the coverage gap directly.

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: fetch any SGS (BCB) series by its numeric code, with the caveat 'quando não está no catálogo'. That distinguishes it from the catalog-driven sibling obter_serie, though the distinction is implied rather than stated outright.

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?

It gives a clear usage condition ('when the series is not in the catalog') and names the alternative for discovering codes ('Use sgs_buscar para achar códigos'). It does not spell out when to prefer obter_serie over this tool, but the catalog reference covers the main routing decision.

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