Skip to main content
Glama
Sign In
wise-mcp

wise-mcp

by Szotasz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_temporary_quote

Read-only

Check exchange rates and fees by generating a temporary quote. Specify source and target currencies to receive instant rate details without creating a stored quote.

Instructions

Get a temporary (non-stored) quote to check rates and fees without creating one

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": {
      "sourceCurrency": "<sourceCurrency>",
      "targetCurrency": "<targetCurrency>"
    },
    "name": "get_temporary_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceAmountNoAmount in source currency (provide this OR targetAmount)
targetAmountNoAmount in target currency (provide this OR sourceAmount)
sourceCurrencyYesSource currency code, e.g. EUR
targetCurrencyYesTarget currency code, e.g. HUF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds behavioral context by emphasizing the temporary, non-stored nature of the quote, which goes beyond the annotations and helps the agent understand the tool's side effects (none persisted).

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 a single, front-loaded sentence that conveys the essential information without any filler or repetition. Every word 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 read-only tool with comprehensive schema descriptions and annotations, the description adequately covers purpose and behavior. It hints at the return content ('rates and fees'), though it does not detail the response structure. Given the absence of an output schema, a slightly more explicit note on the returned data would make it perfect, but it is still complete enough for an agent to use correctly.

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%, with all four parameters individually described. The description itself does not add any parameter-level meaning, but the schema already covers the semantics, so a baseline score 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 action ('Get'), resource ('a temporary (non-stored) quote'), and purpose ('to check rates and fees'). It distinguishes itself from related tools like create_quote by explicitly noting it does not create a stored quote.

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 phrase 'without creating one' implies this tool is for quick checks where persistence is not needed, which provides clear context. However, it does not explicitly name alternative tools (e.g., create_quote) or state when not to use it, so it falls short of a full 5.

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