Skip to main content
Glama

Indicadores Argentina

Inflación entre fechas

inflacion_entre_fechas
Read-only

Inflación acumulada en Argentina entre dos meses, encadenando el IPC mensual del INDEC (no sumando). El mes 'desde' es la base: de agosto a agosto son doce meses. Devuelve el factor, el porcentaje acumulado, el anualizado y cada mes. Si falta un mes publicado lo dice en vez de inventar. Gratis.

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": {
      "desde": "<desde>"
    },
    "name": "inflacion_entre_fechas"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeYesmes base AAAA-MM
hastaNomes final AAAA-MM (default: último IPC publicado)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a safe, closed-world read; the description goes further by disclosing the computation method, the returned fields (factor, accumulated percentage, annualized, per-month breakdown), the missing-data fallback, and that it costs nothing. With no output schema, this carries the return-value burden well.

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?

Five short sentences, front-loaded with the core operation, then the inclusive-base rule, then return shape and edge-case behavior. No sentence is redundant and nothing important is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter computation tool with no output schema, the description covers what is computed, how, what comes back, and what happens when data is missing. Nothing an agent needs in order to call it correctly is absent.

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 semantics beyond it: the 'desde' month is the base and is counted inclusively (August to August = twelve months), which resolves an off-by-one ambiguity the schema's 'mes base AAAA-MM' does not.

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 computation (accumulated inflation in Argentina between two months) with the precise method (chaining INDEC's monthly IPC, not summing), which distinguishes it from generic series siblings like serie_economica. An agent can tell exactly what it computes without opening the schema.

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 clear usage context: 'desde' is the base month, August-to-August counts twelve months, and the tool reports missing published months instead of fabricating data. It never names a sibling (e.g., serie_economica for raw series) or states when not to use it, so it stops short of the 5 bar.

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