Skip to main content
Glama

ipca_detalhado

Read-onlyIdempotent

Break down monthly IPCA, IPCA-15, or INPC inflation by group, item, or subitem to see each component's variation, weight, and contribution in percentage points.

Instructions

Quebras do IPCA (ou IPCA-15, INPC) num mês: variação, peso e contribuição em p.p. de cada componente, desde 2012.

Args: periodo: AAAA-MM; padrão o mais recente. nivel: "grupo", "subgrupo", "item", "subitem" ou "todos". indice: "ipca", "ipca15" ou "inpc". dentro_de: ramo da estrutura pelo código ("1" = alimentação) ou nome. filtro: texto para achar componentes pelo nome ("gasolina"). ordenar: "contribuicao" (padrão), "variacao", "peso" ou "estrutura". limite: linhas devolvidas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ipca_detalhado"
  }
}

Input Schema

NameRequiredDescriptionDefault
nivelNogrupo
filtroNo
indiceNoipca
limiteNo
ordenarNocontribuicao
periodoNo
dentro_deNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 the safety profile is covered. The description adds real context beyond that, namely that only data from 2012 onward exists, that periodo defaults to the most recent month, that the default limit is 40 rows, and that dentro_de accepts either a structure code or a name. It says nothing about what happens with an invalid code, whether limit is capped, or how truncation is signalled.

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-loaded one-sentence summary that states the resource, the metrics and the historical scope, followed by a compact Args block where each line corresponds to exactly one parameter. Given 0% schema coverage the Args list is load-bearing rather than padding, and there is no redundant restatement of the tool name.

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 7-parameter, all-optional analytical tool with no output schema, the description supplies the essentials: scope, defaults, accepted values and the fact that rows contain variação, peso and contribuição. Residual gaps are the return layout beyond those three columns (what identifies each component row) and behaviour on invalid values or beyond the limit.

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

Parameters5/5

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

Schema description coverage is 0% — the properties carry only bare titles and defaults — so the description carries the entire burden, and it does: every one of the seven parameters is explained with accepted values, defaults and a worked example ('1' = alimentação, 'gasolina' for filtro). The analog of an enum is spelled out for nivel, indice and ordenar, which the schema itself leaves as unconstrained strings.

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 opening sentence names the specific resource and metrics: breakdowns of IPCA/IPCA-15/INPC components in a month with variação, peso and contribuição em p.p., plus coverage 'desde 2012'. That is far more specific than a name restatement, but it never names or contrasts a sibling such as ipca_item_historico or obter_serie, so an agent must infer the boundary itself.

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?

Guidance is present only at the parameter level: defaults (periodo = most recent, ordenar = 'contribuicao'), the accepted values of nivel and indice, and the 'dentro_de'/'filtro' narrowing options. There is no statement of when to choose this tool over the related series/sidra/sgs tools, so the when-to-use decision is implied rather than stated.

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