Skip to main content
Glama

get_ipca

Retrieve monthly IPCA inflation rates (% per month) from Banco Central for a selected period of 1–24 months to monitor Brazilian consumer prices.

Instructions

Return the latest monthly IPCA inflation values (% per month) from Banco Central.

Args: last: How many months to return (1 to 24).

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

Input Schema

NameRequiredDescriptionDefault
lastNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals the unit and the source, but says nothing about ordering (newest first?), whether the series is complete or gaps are possible, whether revisions occur, or what errors look like when the range is exceeded — and for a tool with zero annotation coverage these are real gaps.

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?

Two short lines, with the purpose front-loaded before the argument block; nothing is padded. The 'Args:' docstring formatting is slightly mechanical but does not waste words.

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 simple single-parameter read tool this covers purpose, unit, source, and parameter bounds. However, with no output schema, the description should indicate the shape of the returned series (e.g., whether each point carries a reference month/date) — that remains unspecified.

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% — the single parameter 'last' has only a type and default of 12 in the schema. The description compensates by defining its meaning ('how many months to return') and imposing a valid range of 1 to 24, which is information available nowhere else.

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 ('Return the latest monthly IPCA inflation values') and names the data source (Banco Central), plus the unit '% per month'. That is enough to distinguish it from indicator tools like get_selic_rate or get_ptax_rate, though the description never explicitly contrasts itself with them.

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?

Usage is implied by the resource name: fetch recent Brazilian inflation figures. There is no statement of when to prefer this over the sibling rate tools (e.g., IPCA for inflation vs Selic for policy rate), and no preconditions or exclusions are mentioned.

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