Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

Rate on a given date

rate_on

Get the ECB exchange rate for a currency pair on a date. Returns both directions and the actual rate date, using the last published rate on weekends/holidays and shortening out-of-window dates.

Instructions

Call this tool for the ECB rate of one pair on one date. Returns both directions and the rate date, so a reciprocal is never reported as the published figure. A date beyond the free window is shortened, never refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesQuote currency. The rate returned is 1 from = X to
dateYesISO date YYYY-MM-DD. If the ECB published nothing that day - every weekend, 1 January, Good Friday, Easter Monday, 1 May, 25 and 26 December - the last rate published on or before it is returned and the answer names that date. Free covers the last 90 days: an older date is shortened to the oldest free day rather than refused, and rate_date says which day the numbers are really from. Pro covers every date back to 1999-01-04
fromYesBase currency. The ECB quotes every currency per 1 euro, so "the ECB rate for USD" is from EUR to USD, not the other way round; invert only if the user asked for the inverse

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses two non-obvius behaviors: it returns both directions so a reciprocal is never reported as the published figure, and it shortens out-of-window dates rather than refusing them. These are genuine behavioral insights beyond the schema, though response structure and error cases are not detailed.

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?

Three sentences, each earning its place: the purpose is front-loaded, followed by the reciprocal guarantee and the date-shortening edge case. No fluff, no repetition of schema content.

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?

For a simple 3-parameter tool with full schema parameter documentation, the description covers purpose and the two most surprising behaviors. A small gap remains in describing the response shape beyond naming its components, but the tool is otherwise well specified for an agent to call it correctly.

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 each parameter has a rich description, including the inversion caveat on 'from' and holiday/weekend/free-window behavior on 'date'. The description itself adds no new parameter-level meaning, so it earns the baseline 3 rather than higher credit.

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?

The description states a specific verb, resource, and scope: 'Call this tool for the ECB rate of one pair on one date.' It clearly distinguishes the tool from currency-conversion and range-based siblings by emphasizing single-pair/single-date scope. The reciprocal remark adds further identity.

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?

The description gives clear context for when to use the tool: ECB rate, one currency pair, one date. However, it does not explicitly name when-not-to-use or point to alternatives such as rate_history (ranges) or rates_latest (current), even though several for-ex sibling tools exist.

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

Install Server

Other Tools