Skip to main content
Glama

Exchangerate

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Pair

get_pair
Read-onlyIdempotent

Get the current exchange rate between two specific currencies (e.g., USD to EUR). Returns the conversion rate. Use for single currency pair lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget currency code (e.g., "JPY")
fromYesSource currency code (e.g., "USD")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget currency code
fromYesSource currency code
rateYesExchange rate from source to target currency
last_updatedYesTime of last update in UTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "from": "USD",
+    "to": "EUR"
+  },
+  {
+    "from": "GBP",
+    "to": "JPY"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "from": {
+      "description": "Source currency code",
+      "type": "string"
+    },
+    "last_updated": {
+      "description": "Time of last update in UTC",
+      "type": "string"
+    },
+    "rate": {
+      "description": "Exchange rate from source to target currency",
+      "type": "number"
+    },
+    "to": {
+      "description": "Target currency code",
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "rate",
+    "last_updated"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "from": "USD",
-    "to": "EUR"
-  },
-  {
-    "from": "GBP",
-    "to": "JPY"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "from": {
-      "description": "Source currency code",
-      "type": "string"
-    },
-    "last_updated": {
-      "description": "Time of last update in UTC",
-      "type": "string"
-    },
-    "rate": {
-      "description": "Exchange rate from source to target currency",
-      "type": "number"
-    },
-    "to": {
-      "description": "Target currency code",
-      "type": "string"
-    }
-  },
-  "required": [
-    "from",
-    "to",
-    "rate",
-    "last_updated"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "from": {
+      "description": "Source currency code",
+      "type": "string"
+    },
+    "last_updated": {
+      "description": "Time of last update in UTC",
+      "type": "string"
+    },
+    "rate": {
+      "description": "Exchange rate from source to target currency",
+      "type": "number"
+    },
+    "to": {
+      "description": "Target currency code",
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "rate",
+    "last_updated"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "from": "USD",
+    "to": "EUR"
+  },
+  {
+    "from": "GBP",
+    "to": "JPY"
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds that it returns the conversion rate and that the rate is 'current', providing a bit of behavioral context. However, it does not elaborate on data source, rate freshness guarantees, or other limitations, so it adds limited value beyond the annotations.

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 with no filler. It front-loads the core action ('Get the current exchange rate'), provides an example, and a usage note. Every sentence adds value and the structure is ideal for quick parsing.

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?

Given the tool's simplicity, two clearly documented parameters, an output schema, and robust annotations, the description is nearly complete. It states the purpose and usage context. It does not explicitly mention how to handle multiple currency pairs (e.g., pointing to get_rates), which is a minor gap but not critical given the phrase 'single currency pair lookups'.

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?

The input schema provides 100% coverage with descriptions for both 'from' and 'to' parameters. The description's example ('USD to EUR') and phrase 'specific currencies' adds no new semantics beyond what the schema already documents. The baseline of 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's function: getting the current exchange rate between two specific currencies, with an explicit example (USD to EUR). It also distinguishes itself from siblings by specifying 'single currency pair lookups', which contrasts with the likely multi-pair sibling get_rates.

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 gives clear context: 'Use for single currency pair lookups.' This implies when to use it (single pair) and indirectly that multi-pair requests should use another tool (like get_rates). It does not explicitly name alternatives, but the usage context is unambiguous.

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

All Exchangerate toolsInspect
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