Skip to main content
Glama

Create quote

wise_create_quote

Prices a transfer by returning the exchange rate, fees, delivery estimate, and a quote ID used to create a transfer. Moves no money; specify either source or target amount.

Instructions

Price a transfer: returns the rate, fees, delivery estimate and a quote ID (valid ~30 min) needed to create a transfer. Moves no money, but needs a full-access token (read-only tokens get error.quote.mustBeAuthenticated); use wise_get_exchange_rate for rates alone. Give exactly one of sourceAmount or targetAmount.

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": "wise_create_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.
sourceAmountNo
targetAmountNo
targetAccountNoRecipient ID, if already known (gives a more accurate fee)
preferredPayInNoBALANCE to pay from your Wise balance, or BANK_TRANSFERBALANCE
sourceCurrencyYesCurrency you send (ISO 4217, e.g. EUR)
targetCurrencyYesCurrency the recipient gets (ISO 4217, e.g. EUR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark this non-read-only, and the description resolves the resulting ambiguity by stating 'Moves no money' while still requiring a full-access token, including the exact failure mode (error.quote.mustBeAuthenticated) for read-only tokens. The ~30 minute quote validity is operational context found nowhere in the structured fields.

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?

Two dense sentences with no filler: outcome and constraints first, then the auth caveat, then the sibling alternative and the amount exclusivity rule. Every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming what is returned plus the quote's shelf life. Auth requirements, mutual exclusivity of amounts, and the alternative tool are all covered for a 7-parameter creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 71%, and the description adds a genuine constraint the schema cannot express: exactly one of sourceAmount or targetAmount must be supplied. Other parameters (profileId, targetAccount, preferredPayIn) are left to their schema descriptions, which is reasonable given their coverage.

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?

States a specific verb and resource ('Price a transfer') and enumerates the concrete outputs: rate, fees, delivery estimate, and a quote ID. It also explicitly separates itself from wise_get_exchange_rate, so an agent can choose between them without opening either schema.

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?

Gives clear context for use ('needed to create a transfer') and names the alternative for the narrower need ('use wise_get_exchange_rate for rates alone'). It does not explicitly contrast with wise_get_quote for re-reading an existing quote, so the routing guidance is strong but not exhaustive.

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