Skip to main content
Glama

wise_create_quote

Create a Wise money transfer quote by specifying source and target currencies, with optional amounts and profile details.

Instructions

Create a Wise money transfer quote.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceCurrencyYes
targetCurrencyYes
sourceAmountNo
targetAmountNo
profile_idNo
api_keyNo
Behavior1/5

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

No annotations are provided, and the description fails to disclose important behavioral traits such as whether the quote involves a rate lock, expiration, fees, or side effects like storing data. The agent receives no insight into the tool's behavior beyond the basic action.

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

Conciseness2/5

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

The description is extremely short at one sentence, which is conciseness taken too far. It lacks essential details and prioritizes brevity over completeness, making it under-specified rather than efficiently concise.

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

Completeness1/5

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

Given the tool has 6 parameters, no output schema, and no annotations, the description is grossly inadequate. It does not clarify return values, required context (e.g., authentication via api_key), or the difference between sourceAmount and targetAmount inputs.

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

Parameters1/5

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

With 0% schema description coverage, the description should explain the meaning and relationship of parameters like sourceAmount vs targetAmount, and the role of profile_id and api_key. Instead, it adds nothing beyond the schema, leaving the agent to guess parameter semantics.

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?

The description clearly identifies the action ('Create') and the resource ('Wise money transfer quote'), making the basic purpose obvious. However, it does not differentiate this tool from sibling tools like wise_exchange_rates or wise_profile, which could cause confusion for the agent when selecting among similar 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?

The description provides no guidance on when to use this tool versus alternatives like wise_exchange_rates or wise_accounts. There is no mention of prerequisites, context, or situations where this tool is appropriate or inappropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'

If you have feedback or need assistance with the MCP directory API, please join our Discord server