Skip to main content
Glama

obter_serie

Read-onlyIdempotent

Retrieves historical data for a Brazilian macroeconomic indicator, including source, unit, and code. Specify an indicator and optional date range, latest observations, or transformations.

Instructions

Série histórica de um indicador do catálogo, com fonte, unidade e código.

Sem período, traz as observações mais recentes (30 dias úteis, 24 meses, 12 trimestres ou 10 anos).

Args: indicador: id do catálogo (buscar_indicadores), ex.: "selic_meta", "ipca". inicio, fim: AAAA, AAAA-MM, AAAA-MM-DD ou AAAA-T1. ultimos: observações mais recentes. transformacao: variacao_periodo, variacao_anual, diferenca, acumulado_12m, acumulado_ano, soma_12m, media_movel_3m, media_movel_12m, anualizado, mm3m_anualizada ou base_100. Acumulados e anualizados valem para séries em variação % (ex.: ipca); soma_12m, para fluxos.

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": {
      "indicador": "<indicador>"
    },
    "name": "obter_serie"
  }
}

Input Schema

NameRequiredDescriptionDefault
fimNo
inicioNo
ultimosNo
indicadorYes
transformacaoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and openWorld, so the bar is lower; the description adds the important default-window behavior when no period is given. Transformation applicability notes also go beyond annotations, though output format and pagination remain unstated.

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?

The purpose and default-window note are front-loaded, followed by a compact Args block. The Args block is fairly dense but every entry contributes parameter meaning rather than restating the schema.

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?

Covers the primary call path, date formats and transformation semantics, but leaves ambiguous how inicio/fim interact with ultimos and says nothing about output shape (no output schema). Adequate for a read-only fetch, with real gaps on parameter interaction.

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 compensate — and it does document all five parameters: indicador with examples, accepted date formats for inicio/fim, the meaning of ultimos, and an enumerated list of transformacao values. It does not clarify precedence when inicio/fim and ultimos are combined.

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 — retrieves the historical series of a catalog indicator with source, unit and code. It is clearly differentiable from siblings like sgs_serie or ipea_serie because it requires an id from buscar_indicadores.

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 states what happens when no period is supplied (30 business days, 24 months, 12 quarters or 10 years) and points to buscar_indicadores for obtaining the indicator id. It also explains which transformations apply to percent-change series versus flows, but does not name when to use comparar_series or other sibling tools.

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