DatoQA — Historical Exchange Rates

get_exchange_rates

Read-onlyIdempotent

ECB indicative daily currency reference rates against EUR. Not real-time or executable prices; inspect observation_date. Original rates freely available at the cited ECB source.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	No	Optional uppercase currency code, for example USD; omit for all available ECB reference currencies. Values are currency units per one EUR.

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`notice`	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
`selected_rate`	No
`available_currencies`	No
`independently_verified`	No	Official-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

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"

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

A4.1/5.0

Behavior4/5

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

With annotations already declaring readOnly, idempotent, and non-destructive behavior, the description adds meaningful context: rates are indicative daily ECB reference rates, not real-time or executable, and observation_date should be checked. It also notes the original source availability, which is useful for provenance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the essential resource definition, then quickly adds the critical caveat and observation_date guidance. Every clause contributes useful information with no wasted wording.

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?

For a read-only lookup with one optional parameter, full schema coverage, annotations covering safety, and an output schema, the description is complete enough. It states the data nature, usage caveats, and source provenance without needing to explain return values.

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% and the sole optional currency parameter is fully documented in the schema, including format and unit meaning. The description adds no parameter-specific syntax or constraints beyond what the schema already provides.

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 clearly identifies the resource and scope: 'ECB indicative daily currency reference rates against EUR.' It distinguishes this from real-time or executable prices, but does not explicitly differentiate from the closely named sibling get_exchange_rate_history beyond the word 'daily.'

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 context and explicit exclusions: rates are not real-time or executable, and the agent should inspect observation_date. It does not name alternative tools such as get_exchange_rate_history for historical queries, so it stops short of full when-to-use guidance.

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

All DatoQA — Historical Exchange Rates 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?