Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

Latest ECB reference rates

rates_latest

Retrieve current European Central Bank daily reference exchange rates for any base currency, including cross rates via the euro. Shows the rate date and cache age.

Instructions

Call this tool for the most recent European Central Bank daily reference rates, re-expressed against any base. Returns the rates, the ECB rate date they belong to, and how old the local cache is.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoBase currency; defaults to the shared business profile's default_currency, else EUR. A rate of 1.0812 for USD means 1 base = 1.0812 USD. Cross rates go through the euro, the only pair the ECB publishes
quotesNoOnly these currencies, at most 200. Omit for all of them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose useful traits: it returns the ECB rate date and cache age, signaling the result may be cached or stale. It doesn't mention read-only status or network behavior, but 'Returns' implies no side effects and the cache-age note is valuable.

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?

A single dense sentence states purpose and return values with no filler. The cache-age mention is the only extra detail, and it earns its place.

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 optional-parameter read tool, the description covers the purpose, the return payload (rates, date, cache age), and the schema covers parameter details. It could mention historical alternatives or error conditions, but these are not necessary for correct invocation.

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?

The input schema already contains rich descriptions for both parameters, including the default behavior of base and the 200-item limit for quotes. The tool description adds no additional parameter semantics, so the baseline 3 applies given schema coverage of 100%.

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?

States a clear verb+resource: call for the most recent ECB daily reference rates. The phrase 're-expressed against any base' adds specificity beyond the title. It doesn't name sibling tools, but 'latest' and 'ECB' distinguish it from historical or conversion-focused siblings.

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?

Explicitly tells the agent to call it for the most recent ECB reference rates, which is a clear context. It does not mention alternatives like rate_history or fx_rates_for, nor state when not to use it, so it lacks exclusion guidance.

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