Skip to main content
Glama
Sign In

divux

by si.divux
OverviewDiscussionsAdmin

Rates: interest rates now, after inflation

check_rates
Read-only

Returns the central bank's policy rate for a country (Bank for International Settlements, about 40 central banks, the ECB for euro countries), the date it last changed, and the country's latest yearly inflation. For the US, returns Treasury yields from the Treasury's daily par yield curve (1 month to 30 years), each next to the latest 12-month inflation (BLS CPI) as a yield minus trailing CPI, and optionally the interest an amount would earn at one term. Applies to questions about current central-bank policy rates, or US Treasury yields next to inflation. Not investment advice. The change in purchasing power of money from a past year is outside this result.

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

Input Schema

NameRequiredDescriptionDefault
termNoTerm for the interest example; default 1 year
amountNoDollar amount to show interest for
countryNoCountry name or two-letter code; defaults to the United States

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Country name or two-letter code; defaults to the United States",
+  "maxLength": 60,
+  "type": "string"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower; the description still adds source coverage, the US-only conditional branch, and the 'not investment advice' caveat. It doesn't discuss data freshness or latency for what are clearly live external feeds, which would have been the natural next detail.

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?

Dense but front-loaded: what it returns, then the US special case, then scope. Each sentence carries content, though the inflation/CPI clause in the first sentence is a bit tangled and could be split.

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 does the work of sketching return contents (rate, change date, inflation, per-term yields, yield-minus-CPI) and defaults (US, 1 year). Only the physical shape of the response and the behavior when a country has no BIS coverage are left 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 100%, so baseline is 3; the description adds real meaning by clarifying that 'term' and 'amount' belong to the optional interest example and are tied to the US Treasury path rather than the central-bank rate path. That conditional scoping is not stated anywhere in the schema.

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?

Specific verb ('Returns') tied to precise resources: central bank policy rate, the date it last changed, and latest yearly inflation, plus the US Treasury par yield curve branch with yield-minus-CPI. The data provenance (BIS, ~40 central banks, ECB for euro countries, Treasury, BLS CPI) makes the output content unmistakable.

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?

Explicitly states applicability: 'questions about current central-bank policy rates, or US Treasury yields next to inflation.' It also carves out an exclusion ('the change in purchasing power of money from a past year is outside this result'), which routes the agent away, though it never names the likely sibling (check_inflation).

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

All divux 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