mcp-livedatapro

getFxExchangeRates

Real-time foreign exchange (FX) mid-market spot rates, bid/ask spreads, and daily volatility for fiat currency pairs. Use when converting fiat currencies or checking real-time interbank Foreign Exchange (FX) mid-market spot rates, bid/ask spreads, and inverse rates between two 3-letter ISO currency codes. Do not use for cryptocurrency token prices (use getCryptoDexLiquidity) or central bank policy rates (use getCentralBankRates).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "base_currency": "<base_currency>",
      "target_currency": "<target_currency>"
    },
    "name": "getFxExchangeRates"
  }
}

Input Schema

Name	Required	Description	Default
`base_currency`	Yes	3-letter uppercase ISO 4217 base currency code (e.g., USD, EUR, GBP, CHF).
`target_currency`	Yes	3-letter uppercase ISO 4217 quote/target currency code (e.g., EUR, HUF, JPY, GBP).

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / base_currency / examples
```
Added value: +[
+  "USD"
+]
```
- addedInput schema / properties / base_currency / maxLength
```
Added value: +3
```
- addedInput schema / properties / base_currency / minLength
```
Added value: +3
```
- addedInput schema / properties / base_currency / pattern
```
Added value: +"^[A-Z]{3}$"
```
- addedInput schema / properties / target_currency / examples
```
Added value: +[
+  "EUR"
+]
```
- addedInput schema / properties / target_currency / maxLength
```
Added value: +3
```
- addedInput schema / properties / target_currency / minLength
```
Added value: +3
```
- addedInput schema / properties / target_currency / pattern
```
Added value: +"^[A-Z]{3}$"
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / base_currency / description

Previous value: -"3-letter ISO currency code (e.g., USD, EUR, GBP, CHF)"New value: +"3-letter uppercase ISO 4217 base currency code (e.g., USD, EUR, GBP, CHF)."

changedInput schema / properties / target_currency / description

Previous value: -"3-letter ISO target currency code (e.g., EUR, HUF, JPY)"New value: +"3-letter uppercase ISO 4217 quote/target currency code (e.g., EUR, HUF, JPY, GBP)."

First observedOct 21, 2026

TDQS

A4.1/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 full behavioral burden. It does disclose the data contents (mid-market spot, bid/ask spread, daily volatility, inverse rates) and signals freshness ('real-time'), but says nothing about rate limits, caching, auth requirements, or whether spreads/volatility are always present for every pair — gaps that matter for a data-fetch tool with zero annotation coverage.

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?

Usage and exclusions are front-loaded and the text is short. Minor waste: the 'mid-market spot rates, bid/ask spreads' phrase is repeated almost verbatim in the second sentence, which could be trimmed.

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?

With no output schema, the description helpfully enumerates the returned data points (spot rate, bid/ask, volatility, inverse rate), which compensates well. It stops short of describing response structure or handling of unsupported/illiquid pairs, so it is strong but not fully complete.

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 both parameters are fully documented in the schema itself. The description only echoes 'two 3-letter ISO currency codes' without adding format or constraint detail beyond the schema; baseline 3 applies.

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?

Names a specific resource (FX mid-market spot rates, bid/ask spreads, volatility) and the scope (fiat currency pairs defined by two ISO codes). Explicitly excludes cryptocurrency and central bank rates, naming the sibling tools to use instead, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit 'use when' (converting fiat currencies, checking interbank spot/bid-ask/inverse rates) and an explicit 'do not use for' with named alternatives (getCryptoDexLiquidity, getCentralBankRates). Both the positive and negative routing conditions are stated.

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

All mcp-livedatapro 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?