Skip to main content
Glama

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

getCentralBankRates

Official central bank policy interest rates, quantitative tightening status, and upcoming rate decision calendar. Use when querying official macroeconomic central bank policy interest rates, recent basis-point changes, next FOMC/MPC meeting dates, and implied rate-cut probabilities. Do not use for retail consumer mortgage/auto loan APRs (use getConsumerLoanRates) or FX currency spot rates (use getFxExchangeRates).

Input Schema

NameRequiredDescriptionDefault
central_bankYesStandardized central bank identifier (FED, ECB, BOE, BOJ, SNB, BOC, RBA, PBOC, MNB).FED

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / central_bank / default
      Added value: +"FED"
    • addedInput schema / properties / central_bank / enum
      Added value: +[
+  "FED",
+  "ECB",
+  "BOE",
+  "BOJ",
+  "SNB",
+  "BOC",
+  "RBA",
+  "PBOC",
+  "MNB"
+]
    • addedInput schema / properties / central_bank / examples
      Added value: +[
+  "FED"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / central_bank / description
      Previous value: -"Central bank code or country (e.g., FED, ECB, BOE, BOJ, SNB)"New value: +"Standardized central bank identifier (FED, ECB, BOE, BOJ, SNB, BOC, RBA, PBOC, MNB)."
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully enumerates the data payloads returned (policy rate, QT status, decision calendar, implied probabilities), but says nothing about data freshness/delay, update cadence, coverage gaps for banks outside the enum, or error/auth behavior — meaningful omissions for a financial-data tool.

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?

Three front-loaded sentences with the purpose first and routing last; no filler. Minor redundancy between 'Official central bank policy interest rates' in sentence one and 'official macroeconomic central bank policy interest rates' in sentence two, which restates the same resource.

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 one enum parameter, no annotations, and no output schema, the description does the necessary work: it defines scope, enumerates the returnable data domains, and routes to alternatives. The remaining gap is timeliness/freshness expectations, which matter for rate and meeting-calendar data but are not stated.

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% with a fully enumerated central_bank parameter, so the schema already documents it. The description adds only the implied multi-bank framing via 'FOMC/MPC' and does not explain default behavior or whether omitting the parameter is possible. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb+resource ('Official central bank policy interest rates, quantitative tightening status, and upcoming rate decision calendar') and explicitly names the sibling tools it is not (getConsumerLoanRates, getFxExchangeRates). An agent can distinguish it from the 40+ siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use when...' clause covering the intended queries (policy rates, basis-point changes, FOMC/MPC dates, implied cut probabilities) and an explicit 'Do not use for...' clause routing to two named alternatives. Both the positive and negative boundaries are stated.

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

All mcp-livedatapro 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