DatoQA — Economic Indicators

get_interest_rates

Read-onlyIdempotent

Canadian overnight_target or bank_rate, in percent. Default: latest published numeric observation. Optional year or exact source date, mutually exclusive. Daily observations since 2010; never infer missing dates or decision announcement/effective dates. Not real-time or retail loan quotes. Source, decimals and evidence retained; original data free at Bank of Canada.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Exact source date YYYY-MM-DD; no carry-forward for missing dates. Cannot be combined with year.
`year`	No	Source calendar year since 2010; omit for latest observation. Cannot be combined with date.
`series`	Yes	Canadian policy series: overnight_target or bank_rate. Both are percentages, not retail rates.

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`notice`	No
`series`	No
`status`	Yes	Read this before using values; a successful transport does not establish data availability.
`returned`	Yes	Domain-specific result count, not necessarily the number of stored records in items.
`directory`	No
`latest_only`	No
`requested_date`	No
`available_years`	No
`independently_verified`	No	Official-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

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"
+]

First observedSep 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the bar is lower; the description still adds real behavioral context: coverage begins 2010, missing dates must never be inferred or carried forward, announcement/effective dates are out of scope, and source/decimals/evidence are retained with the result.

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?

It is compact and front-loads the resource and unit before the parameter rules. The telegraphic phrasing ('Optional year or exact source date, mutually exclusive') is slightly clipped and the closing licensing note is marginal, but nothing is bloated.

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 an output schema present, return values need not be described. The description covers defaults, date range, unit semantics, and exclusions, leaving only minor gaps such as whether a year returns multiple observations or how many.

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 all three parameters are already documented, including the year/date mutual exclusion. The description reinforces units (percent, not retail) and the latest-by-default behavior but adds little syntax or format detail beyond the schema, matching the baseline 3.

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 the resource (Canadian policy rates) and the exact series values (overnight_target, bank_rate) plus the unit (percent), which distinguishes it from siblings like get_exchange_rates and get_economic_indicators. It never states an explicit retrieval verb, but the resource and scope are unambiguous.

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?

It gives clear usage conditions: default is the latest published observation, year and date are mutually exclusive, and it explicitly excludes real-time data and retail loan quotes. It stops short of naming an alternative sibling tool (e.g., list_interest_rate_series) for the excluded cases, so it is not a full when/when-not/alternative statement.

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

All DatoQA — Economic Indicators 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.

Resources

Need Help?