Skip to main content
Glama

ipea_serie

Read-onlyIdempotent

Fetch Ipeadata series by code with optional period, latest-values, or territory filters; returns observations, metadata, and original source for analysis.

Instructions

Série do Ipeadata pelo código, com metadados e fonte original. O Ipeadata redistribui dados de IBGE, BCB, Receita, ANP etc. Séries de fonte privada (FGV, CNI, Anfavea...) ficam bloqueadas por padrão. Sem período, traz as observações mais recentes. Localize o código com ipea_buscar.

Args: codigo: ex.: "CAGED12_SALDON12". inicio, fim, ultimos: período e recorte, como em obter_serie. territorio: só séries regionais: "0" Brasil, "1" a "5" regiões, "35" ou "SP" UF, 7 dígitos município.

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

Input Schema

NameRequiredDescriptionDefault
fimNo
codigoYes
inicioNo
ultimosNo
territorioNo

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 declare readOnly, idempotent, openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: results include metadata and original source, private-source series (FGV, CNI, Anfavea) are blocked by default, and no period yields the latest observations.

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?

Front-loads the core operation, then layers useful constraints (private-source blocking, default recency, code lookup) and a parameter block that maps directly onto usage. No sentence is redundant.

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?

There is no output schema, and while the description says metadata and original source are returned, it does not describe the shape of the observation results. Combined with undocumented date formats for inicio/fim, an agent has enough to call the tool but not to fully anticipate the response.

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 coverage is 0%, so the description must compensate, and it does so unevenly. It documents codigo with an example and gives a precise territory mapping ("0" Brazil, "1"-"5" regions, "35" or "SP" state, 7-digit municipality), but inicio and fim formats are only cross-referenced to obter_serie and ultimos is not explained at all.

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?

States a specific verb and resource: fetch an Ipeadata series by code, returning metadata and the original source. It also distinguishes the lookup step by naming ipea_buscar for finding the code, though its relationship to the sibling obter_serie (which it only references for period handling) is left unclear.

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?

Gives useful guidance: locate the code with ipea_buscar first, and omitting a period returns the most recent observations. However, it never explains when to prefer ipea_serie over obter_serie, which the description itself invokes as the model for period parameters, so the agent must infer which tool to pick.

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