Skip to main content
Glama

Argentina inflation (INDEC)

ar_inflacion
Read-onlyIdempotent

Argentine consumer price inflation from INDEC: latest monthly %, year-over-year %, last 12 months, and optionally the compounded cumulative inflation between two months with an amount adjusted for inflation (rent, salary, price updates). Send {} or {from: YYYY-MM, to: YYYY-MM, amount}. Source failure = no charge. Paid tool: 0.002 USDC per call via x402 (USDC on Base, Polygon or Solana, no account or key). An unpaid call returns a payment-required result (isError, structuredContent with x402Version 2 and accepts); sign one of the accepts and retry the same call with the PaymentPayload in params._meta["x402/payment"]. Returns JSON text; the settlement is in result._meta["x402/payment-response"].

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

Input Schema

NameRequiredDescriptionDefault
toNoLast month YYYY-MM (inclusive, default latest)
fromNoFirst month YYYY-MM (inclusive)
amountNoAmount in ARS to adjust

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it declares the paid x402 model (0.002 USDC, chains accepted, no account/key needed), what an unpaid call returns (isError plus structuredContent with x402Version and accepts), exactly how to retry with the PaymentPayload in params._meta, and where settlement appears. It also discloses the "source failure = no charge" policy, which the agent could not infer from readOnly/idempotent hints alone.

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?

Purpose and modes come first, then payment mechanics, which is a sensible front-loading. It is dense but every sentence carries information: the payment flow and settlement location are operational necessities rather than filler. Marginally long, but not padded.

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?

With no output schema, the description compensates by enumerating the returned data (monthly %, YoY %, 12-month series, cumulative adjustment) and pointing to result._meta for settlement. Only the exact JSON shape of the inflation payload is left implicit, which is a minor gap for a read-only lookup tool.

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 100%, so the baseline is 3, but the description adds real meaning: the empty-object form is the default latest reading, and the from/to/amount triple triggers compounded cumulative mode with the amount adjusted for inflation for use cases like rent or salary updates. It clarifies how the parameters interact rather than just restating their types.

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 resource (Argentine CPI from INDEC) and precisely what it returns: monthly %, YoY %, trailing 12 months, plus an optional compounded cumulative between two months with an ARS amount adjusted. This clearly separates it from siblings like ar_dolar, fx_rate or ar_cbu, which deal with exchange rates and other Argentine data rather than inflation indices.

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?

Gives both invocation shapes explicitly ("Send {} or {from, YYYY-MM, to, YYYY-MM, amount}"), which tells the agent how to choose between simple and cumulative mode. It also spells out the payment retry path. It does not explicitly exclude or compare itself with siblings such as fx_rate, but the domain difference is obvious from the purpose statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources