Skip to main content
Glama
Sign In
Wise MCP Server

Wise MCP Server

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wise_get_exchange_rate

Read-only

Obtain the current mid-market exchange rate for any currency pair to compare conversion rates.

Instructions

Get the current mid-market exchange rate between two currencies.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "wise_get_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource currency code, ISO-4217 (e.g. EUR, USD, GBP)
targetYesTarget currency code, ISO-4217

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so description carries low burden. Description adds that the rate is 'current mid-market', which is useful but does not elaborate on side effects, rate limits, or response structure.

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?

Single sentence of 12 words, highly efficient and front-loaded with the core purpose. No unnecessary details.

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?

Tool is simple with two well-documented parameters and no output schema. Description plus annotations provide adequate context, though a note about the return format would improve completeness.

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 covers both parameters with clear descriptions (ISO-4217 codes). Tool description does not add further meaning beyond what schema already provides, 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?

Description clearly states the tool gets the current mid-market exchange rate between two currencies, specifying verb, resource, and key qualifications. It distinguishes itself from siblings like wise_get_exchange_rate_history and list tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as wise_get_exchange_rate_history or other rate-related tools. Does not mention prerequisites, filtering, or scenarios where this tool is or is not appropriate.

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

Deploy Server

Other Tools