Skip to main content
Glama
luno

Luno MCP Server

Official
by luno

convert

Destructive

Convert funds between two currency accounts instantly using the broker quote. Use idempotency key to safely retry without double-converting. Requires --allow-write-operations flag.

Instructions

Instantly convert funds between two currency accounts on the authenticated profile via the Luno broker (e.g. ZAR to ZARU). The conversion is final and applies the broker quote at execution time. Pass idempotency_key to make retries safe; omitting it generates a fresh UUID per call, so retries on network error may double-convert. Write operation: requires the --allow-write-operations flag or ALLOW_WRITE_OPERATIONS=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount of the source currency to convert, as a decimal string (e.g. "100.00"). Must be positive.
idempotency_keyNoAny unique string up to 255 chars. Reuse the same key to safely retry a failed call without double-converting. Auto-generated as a UUID when omitted.
source_account_idYesNumeric ID of the account to debit, as a string (from get_balances).
target_account_idYesNumeric ID of the account to credit, as a string (from get_balances). Must hold the target currency.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
converted_amountYes
idYes
source_account_balanceYes
source_currencyYes
target_account_balanceYes
target_currencyYes
Behavior5/5

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

Annotations indicate destructiveHint=true and idempotentHint=false. The description reinforces this by stating the conversion is final, warns about double-conversion, and clarifies the broker quote at execution time. No contradiction.

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 two sentences plus a note about the write flag. It is front-loaded with the core purpose and uses minimal but essential words. Every sentence adds value.

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?

Given the tool is a destructive write with an output schema (not shown), the description covers key operational aspects: finality, quote timing, idempotency, and auth requirements. It does not detail failure modes or return values, but those are likely in the output schema.

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

Parameters5/5

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

Schema description coverage is 100%, and the description adds critical context: idempotency_key behavior (auto-generated UUID vs. user-supplied), amount must be positive decimal string, and account IDs come from get_balances. This significantly aids parameter understanding.

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 action ('convert funds between two currency accounts'), specifies the broker (Luno), and provides an example ('ZAR to ZARU'). This matches the sibling context: no other tool performs conversions, so it is well-differentiated.

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 description explains when to use the tool (e.g., for instant conversions), the importance of idempotency_key for retry safety, and the required write flag. It does not explicitly mention alternatives but covers key usage guidance.

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/luno/luno-mcp'

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