Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_currency_and_crypto_rate

Fetch live European Central Bank (ECB) foreign exchange rates (USD, CHF, GBP, PLN, JPY, TRY) and real-time Bitcoin/Ethereum/Solana spot prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_currency_and_crypto_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoCurrency or crypto ticker (e.g. BTC, ETH, SOL, USD, CHF, GBP, PLN)
amount_eurNoAmount in EUR to convert (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully names the data source (ECB) and states the data is live/real-time, which is meaningful behavioral context, but it omits rate limits, caching/freshness semantics, error behaviour for unknown tickers, and whether the base currency is always EUR.

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 front-loaded sentence with the verb first and the two data families clearly enumerated. There is no filler, hedging, or restatement of the title.

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 two-parameter lookup with no output schema, the description covers the data sources and supported assets adequately. The remaining gap is the shape of the response — it is unclear whether a call returns one computed rate for the given asset/amount or a full rate table — which matters in the absence of an output schema.

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 the schema already documents both `asset` (with example tickers) and `amount_eur` (default 100). The description adds no parameter-level meaning beyond what the schema states — it never mentions the conversion amount or how the asset ticker is resolved. Baseline 3 is appropriate.

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?

States a specific verb ("Fetch") and two precisely named resources (ECB foreign exchange rates and Bitcoin/Ethereum/Solana spot prices), and even enumerates the supported fiat tickers. An agent can immediately tell this is a market-rate lookup, distinct from every sibling tool in the set (heating oil, weather, traffic, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through qualifiers like "live" and "real-time", which signal a current-rate lookup rather than historical data. However, it never states when to call it versus not, whether there are any prerequisites, or what to do with unsupported tickers — the agent must infer everything from the name and field list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources