APIVerve

Interest Rate

InterestRate

Read-only

Interest Rate: Interest Rate retrieves central bank policy rates for 22 major economies by country code. It delivers the latest interest rate percentage, central bank name, recorded date, and whether the rate moved up, down, or remained unchanged, while paid plans add the 12-month change, the 12-month high, low and average, and the last 12 monthly rates. (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": "InterestRate"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional month in YYYY-MM format for a historical lookup. Omit for the current rate.
`changes`	No	Include the 12-month change and the 12-month high, low and average
`country`	Yes	2-letter country code
`history`	No	Include the 12 monthly rates ending at the returned month

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses two genuinely useful traits: the paid-plan gating of the 12-month change/high/low/average and monthly history, and a cost of 2 credits. It doesn't cover rate limits or error behavior for invalid country codes, but the plan and cost disclosure is substantive added value.

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 core purpose and scope are front-loaded in the first sentence, with field/plan detail and cost following. The name/title is restated at the start ('Interest Rate: Interest Rate retrieves...'), which is minor waste, but the rest is dense and earns its place.

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?

With an output schema present, the description doesn't need to enumerate return values, yet it still gives enough shape (rate, central bank, date, direction) plus cost and plan restrictions so an agent can decide to call it confidently. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so the schema already explains country, date, changes, and history. The description corroborates that country selects among 22 economies and loosely maps the paid-plan extras to the changes/history flags, but adds no format or edge-case detail (e.g., accepted country-code casing, behavior when a month has no record).

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?

The description opens with a specific verb and resource ('retrieves central bank policy rates') and scopes it to '22 major economies by country code' and the fields returned. This clearly separates it from siblings such as BenchmarkRate, MortgageRate, or InflationRate, which cover different rate concepts.

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?

The context of use is implied by the country-code input and the current-vs-historical framing, but no explicit when-to-use statement, prerequisites, or named alternatives are given. An agent must infer that this is the tool for central bank policy rates rather than, say, BenchmarkRate or TreasuryYields.

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

All APIVerve tools Inspect

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.