Skip to main content
Glama

DatoQA

by dev.workers.bhazarstudio.datoqa
OverviewDiscussionsAdmin

get_interest_rates

Read-onlyIdempotent

Retrieve or export central-bank policy rates in percent. provider=boe series=bank_rate since 1975; boc default overnight_target/bank_rate since 2010; ecb deposit_facility/main_refinancing/marginal_lending and historical main_refinancing_minimum_bid since 1999; fed eight series from directory with distinct starts since 1982. Latest numeric observation by default, optional year or exact date (mutually exclusive). format=csv provides a ready-to-import table with notes and provenance. No date filling, inferred announcement dates or retail quotes. Historical instruments are not current rates. Original source data free; not independently verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoExact published source date YYYY-MM-DD. Mutually exclusive with year; no carry-forward or inferred rate for a missing date.
yearNoOne source calendar year, within this provider and series coverage and no later than the current year. Mutually exclusive with date; omit both for the latest numeric observation.
formatNoCSV includes selected observations, original decimals, null flags, definitions and provenance. MCP returns CSV content alongside JSON; source-date gaps keep JSON only.json
seriesYesProvider-specific policy series from list_interest_rate_series. For example boe/bank_rate or ecb/deposit_facility; incompatible provider/series pairs are rejected.
providerNoCentral bank: boc Canada (default), ecb euro area, fed United States, or boe United Kingdom. Select a series from this provider.boc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
noticeNo
seriesNo
statusYesRead this before using values; a successful transport does not establish data availability.
returnedYesDomain-specific result count, not necessarily the number of stored records in items.
directoryNo
latest_onlyNo
requested_dateNo
available_yearsNo
independently_verifiedNoOfficial-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"Exact published source date YYYY-MM-DD. Mutually exclusive with year; no carry-forward or inferred rate for a missing date."
    • addedInput schema / properties / provider / description
      Added value: +"Central bank: boc Canada (default), ecb euro area, fed United States, or boe United Kingdom. Select a series from this provider."
    • addedInput schema / properties / series / description
      Added value: +"Provider-specific policy series from list_interest_rate_series. For example boe/bank_rate or ecb/deposit_facility; incompatible provider/series pairs are rejected."
    • addedInput schema / properties / year / description
      Added value: +"One source calendar year, within this provider and series coverage and no later than the current year. Mutually exclusive with date; omit both for the latest numeric observation."
  2. Changed4 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "description": "CSV includes selected observations, original decimals, null flags, definitions and provenance. MCP returns CSV content alongside JSON; source-date gaps keep JSON only.",
+  "enum": [
+    "json",
+    "csv"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "boc",
-  "ecb",
-  "fed"
-]New value: +[
+  "boc",
+  "ecb",
+  "fed",
+  "boe"
+]
    • changedInput schema / properties / year / maximum
      Previous value: -2026New value: +9007199254740991
    • changedInput schema / properties / year / minimum
      Previous value: -1982New value: +1975
  3. Changed6 schema fields changed
    • removedInput schema / properties / date / description
      Removed value: -"Exact source date YYYY-MM-DD; no carry-forward for missing dates. Cannot be combined with year."
    • addedInput schema / properties / provider
      Added value: +{
+  "default": "boc",
+  "enum": [
+    "boc",
+    "ecb",
+    "fed"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / series / description
      Removed value: -"Canadian policy series: overnight_target or bank_rate. Both are percentages, not retail rates."
    • changedInput schema / properties / series / enum
      Previous value: -[
-  "overnight_target",
-  "bank_rate"
-]New value: +[
+  "overnight_target",
+  "bank_rate",
+  "deposit_facility",
+  "main_refinancing",
+  "main_refinancing_minimum_bid",
+  "marginal_lending",
+  "federal_funds_target",
+  "federal_funds_lower",
+  "federal_funds_upper",
+  "reserve_balances",
+  "excess_reserves",
+  "required_reserves",
+  "primary_credit",
+  "overnight_reverse_repo"
+]
    • removedInput schema / properties / year / description
      Removed value: -"Source calendar year since 2010; omit for latest observation. Cannot be combined with date."
    • changedInput schema / properties / year / minimum
      Previous value: -2010New value: +1982
  4. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / provenance / properties / verification_level / enum
      Previous value: -[
-  "official_source_and_schema_checked",
-  "method_specific"
-]New value: +[
+  "official_source_and_schema_checked",
+  "public_aggregator_and_schema_checked",
+  "method_specific"
+]
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), so the burden is lighter. The description still adds real behavioral context beyond them: no carry-forward/inferred rates, historical instruments are not current rates, and source data is free but unverified. It does not describe rate limits or error surface, keeping it below a 5.

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?

Front-loaded with the core purpose, then dense supporting detail. Every sentence carries information (coverage, defaults, exclusions, provenance). It is a single dense paragraph that is effortful to scan but not padded.

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 5 params, full schema coverage, and an output schema that handles return values, the description covers the remaining gaps: provider/series mapping, date vs year exclusivity, CSV behavior, and data-quality caveats. It is essentially complete for correct invocation, missing only sibling routing.

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 value beyond the schema by tying specific series to providers and their coverage windows (boe/bank_rate since 1975, boc since 2010, ecb since 1999, fed eight series since 1982) and by clarifying how format=csv behaves. This meaningfully enriches the enum choices.

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+resource ('Retrieve or export central-bank policy rates in percent') with explicit provider/series coverage and start dates, so it is clearly distinguishable from siblings like get_economic_indicators or get_exchange_rates. An agent knows exactly what data domain this returns.

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?

States default behavior (latest numeric observation), the date/year mutual exclusivity, and the export path via format=csv. It also gives exclusion guidance ('No date filling, inferred announcement dates or retail quotes'). It stops short of naming a sibling as the alternative for related needs (e.g., list_interest_rate_series to discover pairs), so it is clear but not fully routing.

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

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