exchangerate

Get Rates

get_rates

Read-onlyIdempotent

Get current exchange rates for a base currency (e.g., 'USD', 'EUR'). Returns conversion rates for all major currencies. Use when you need multiple rates at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`base_currency`	Yes	ISO 4217 currency code to use as the base (e.g., "USD", "EUR", "GBP")

Output Schema

TableJSON Schema

Name	Required	Description
`base`	Yes	Base currency code
`rates`	Yes	Map of currency codes to exchange rates
`rate_count`	Yes	Number of exchange rates returned
`next_update`	Yes	Time of next update in UTC
`last_updated`	Yes	Time of last update in UTC

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "base": {
+      "description": "Base currency code",
+      "type": "string"
+    },
+    "last_updated": {
+      "description": "Time of last update in UTC",
+      "type": "string"
+    },
+    "next_update": {
+      "description": "Time of next update in UTC",
+      "type": "string"
+    },
+    "rate_count": {
+      "description": "Number of exchange rates returned",
+      "type": "integer"
+    },
+    "rates": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "description": "Map of currency codes to exchange rates",
+      "type": "object"
+    }
+  },
+  "required": [
+    "base",
+    "last_updated",
+    "next_update",
+    "rate_count",
+    "rates"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "base_currency": "USD"
+  },
+  {
+    "base_currency": "EUR"
+  }
+]

First observedApr 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds that rates are 'current' and returns 'all major currencies,' but does not disclose rate source, validity, or error behavior. This is acceptable given annotations but not rich.

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?

The description is two sentences, front-loaded with purpose, then return scope and a usage hint. No wasted words, each sentence 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 one-parameter tool with a rich annotation set and an output schema, the description is complete enough. It covers what it does, what it returns, and when to use it. Minor vagueness about 'all major currencies' is acceptable.

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%, with base_currency fully described as an ISO 4217 code with examples. The description repeats examples ('USD', 'EUR') but adds no additional meaning or context beyond the schema, so 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?

The description clearly states the tool gets current exchange rates for a base currency, which is specific and distinguishes it from the sibling 'get_pair' by noting it returns all major currencies at once. The verb 'Get' and resource 'exchange rates' are explicit.

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?

The description provides a clear usage context: 'Use when you need multiple rates at once.' This implies a single pair tool (like get_pair) would be more appropriate for one rate, though it does not explicitly name alternatives or exclusions.

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

All exchangerate tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.