Exchange Rate MCP

Query Exchange Rate

query_exchange_rate

查询实时汇率并可做金额换算。base基准货币（代码或中文名），target目标货币，留空返回常用货币汇率；amount可选换算金额。主源Frankfurter(ECB)，备源open.er-api.com。

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": "query_exchange_rate"
  }
}

Input Schema

Name	Required	Description	Default
`base`	No	基准货币，代码或中文名均可，默认美元	USD
`amount`	No	可选，要换算的金额
`target`	No	目标货币，代码或中文名均可；留空返回常用货币汇率

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / amount / description
```
Added value: +"可选，要换算的金额"
```
removedInput schema / properties / amount / title
```
Removed value: -"Amount"
```

addedInput schema / properties / base / description

Added value: +"基准货币，代码或中文名均可，默认美元"

removedInput schema / properties / base / title
```
Removed value: -"Base"
```

addedInput schema / properties / target / description

Added value: +"目标货币，代码或中文名均可；留空返回常用货币汇率"

removedInput schema / properties / target / title
```
Removed value: -"Target"
```

removedInput schema / title

Removed value: -"query_exchange_rateArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.9/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 disclosure burden and does add real value by naming the data sources (Frankfurter/ECB as primary, open.er-api.com as fallback), which tells the agent about data provenance and failover behavior. It does not cover error behavior when both sources fail or any rate limits, leaving a modest gap.

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?

The definition is compact and front-loads the capability, then parameters, then data sources. Some parameter text duplicates the schema, but the total length is small and every sentence is on-topic.

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 three-parameter read tool with an output schema, the description covers defaults, the empty-target case, and source fallback, which is enough to invoke correctly. Only failure-mode and precision details are absent, which the output schema likely absorbs.

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 coverage is 100%, so all three parameters are already documented in the input schema. The description largely restates the same defaults and the empty-target behavior, adding little meaning beyond the schema; baseline 3 applies.

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 states a specific verb and resource — querying live exchange rates — and adds the secondary capability of amount conversion. It is immediately clear what the tool returns, though there is no sibling tool to distinguish it from.

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?

Usage context is given clearly: base defaults to USD, an empty target returns a set of common currency rates, and amount is optional for conversion. There are no exclusions or alternatives, but with no sibling tools none are needed.

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

All Exchange Rate MCP 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.