Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Inflation Rate

InflationRate
Read-only

Inflation Rate: Inflation Rate reports annual inflation rates and Consumer Price Index (CPI) values for any country by two-letter country code. Outputs include the year-over-year price change percentage, CPI index, and base comparison year, with paid plans supporting historical lookups by year. On paid plans, changes=true adds the prior year's rate and the change from it, plus the 5-year average, high, low and cumulative CPI rise. (Cost: 2 credits)

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": {
      "country": "<country>"
    },
    "name": "InflationRate"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoThe year to retrieve data for. Defaults to the previous year.
changesNoInclude the previous year's rate, the change from it, and the 5-year average, high, low and CPI rise
countryYesISO 2-letter country code (e.g., US, GB, JP, DE, BR)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), but the description adds real context beyond them: a paid-plan gating of year-based historical lookups and a credit cost of 2. Those are exactly the operational constraints an agent needs before calling, though nothing is said about error behavior for invalid country codes.

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?

The description is front-loaded with the core purpose and return values, then plan/credit conditions, and every sentence carries information. The opening 'Inflation Rate: Inflation Rate reports' redundantly restates the name, and the parenthetical cost could be tighter, but overall it is well structured.

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 three-parameter read tool with an output schema and full schema coverage, the description is nearly complete: it covers output contents, plan limits, the changes flag's effect, and cost. The remaining gap is the absence of any disambiguation from closely related inflation/CPI siblings, which leaves an agent without routing criteria.

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 100%, so the baseline is 3, and the description largely repeats what the schema already says about changes (prior year's rate, delta, 5-year average, high, low, CPI rise). The one genuine addition is that historical `year` values are gated behind paid plans, which is not in the schema and is useful, but it is a small increment.

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 description names a specific verb and resource: reports annual inflation rates and CPI values for a country given a two-letter code, and enumerates returned fields (YoY change %, CPI index, base year). It is clear what the tool does, but it never distinguishes itself from the near-identical sibling CPIInflation, which an agent would have trouble choosing between.

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 only implied: the description notes that historical lookups by year require a paid plan and explains when changes=true is worthwhile, which helps an agent decide call shape. However, it gives no when-to-use-vs-alternative guidance — CostofLiving, PurchasingPower, and especially CPIInflation are obvious competitors and none are mentioned or excluded.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources