MCP tool: get_rate
Read a stored direct currency rate. Billable: yes (1 request unit).
Need this over REST instead? See
GET /v1/rates/{base}/{quote} →.
Input
{ "base": "EUR", "quote": "USD" }Output — success
Identical field set to the REST current-rate endpoint’s 200 body:
{
"base": "EUR",
"quote": "USD",
"rate": "1.174582",
"as_of": "2026-09-29T11:41:32.241582Z",
"type": "direct"
}rate is an exact decimal string. as_of is RFC3339Nano UTC. type is
always "direct" today.
Raw JSON-RPC example
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_rate",
"arguments": { "base": "EUR", "quote": "USD" }
}
}{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [{ "type": "text", "text": "..." }],
"structuredContent": {
"base": "EUR",
"quote": "USD",
"rate": "1.174582",
"as_of": "2026-09-29T11:41:32.241582Z",
"type": "direct"
}
}
}Errors
| Code | Meaning |
|---|---|
invalid_asset_symbol | base/quote format invalid |
unsupported_pair | Syntactically valid pair, not currently supported |
temporarily_unavailable | Storage/dependency failure |
quota_exceeded | Request-unit quota exhausted for the billing period |
All errors are returned as CallToolResult{IsError: true} with
{code, message, request_id} in structured content (quota_exceeded also
carries limit/remaining/reset_at) — not an HTTP status code. See
MCP overview and Errors.