Skip to main content
Glama

Get quote

wise_get_quote
Read-only

Retrieve an existing Wise quote by UUID to review exchange rates, fees, and transfer details before creating or funding a transfer.

Instructions

Fetch an existing quote by ID.

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": {
      "quoteId": "<quoteId>"
    },
    "name": "wise_get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYesQuote ID (UUID)
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no note on quote expiry, error behavior for an invalid/expired ID, or whether a remote lookup can fail. Nothing is contradicted, but nothing is contributed either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded and free of filler; it earns its place, though it is so terse that it borders on under-specification rather than model conciseness.

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

Completeness3/5

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

For a two-parameter read-only lookup with fully documented params, declared annotations, and no output schema, the definition is minimally sufficient. It could still say what a quote contains or how expired quotes behave, which matters for an openWorld fetch.

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%, including the note that profileId is optional when WISE_PROFILE_ID is set and can be sourced from wise_list_profiles. The description only echoes the quoteId lookup, so baseline 3 applies with the schema doing the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetch an existing quote by ID" names a specific verb (fetch), resource (quote), and lookup key, and the word "existing" implicitly separates it from wise_create_quote. It does not explicitly name a sibling, so it stops short of full differentiation.

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?

There is no when-to-use guidance, no prerequisites (e.g., that a quote ID must have been produced by wise_create_quote), and no mention of alternatives. An agent must infer the usage context entirely from the tool name and schema.

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