Skip to main content
Glama

CryptoBuddy

by au.com.cryptobuddy
OverviewDiscussionsAdmin

find_best_australian_exchange

Compare Australian cryptocurrency exchanges to identify the best estimated buying or selling outcome for a specified asset, AUD trade amount and direction. Use this tool when the user wants to compare exchange prices, fees or estimated value received. For simply finding exchanges that offer a cryptocurrency, use find_where_to_buy_crypto instead. Results are estimates, not guaranteed executable quotes, and no trade is placed. This is a paid data-access tool using XRP on XRPL Mainnet. First call without paymentSignature to receive an x402 v2 payment challenge. An authorised compatible payer must generate the PAYMENT-SIGNATURE for the exact resource and retry with identical inputs. Never supply wallet secrets. This server does not sign or initiate payments. If payment fails or times out, verify settlement before attempting another payment.

Input Schema

NameRequiredDescriptionDefault
sideNoTrade direction: buy spends AUD to acquire the asset; sell quotes disposal into AUD. Defaults to buy.buy
assetYesCryptocurrency symbol, for example XRP, BTC or ETH
amountNoTrade amount in Australian dollars (AUD), not the API access price. Defaults to 1000; must be positive.
paymentSignatureNoOptional base64 x402 v2 PAYMENT-SIGNATURE header generated by an authorised payer for the exact resource returned by an unpaid call. Omit to request a challenge. This is a payment payload, never a seed, private key, or password.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in Australian dollars"New value: +"Trade amount in Australian dollars (AUD), not the API access price. Defaults to 1000; must be positive."
    • addedInput schema / properties / paymentSignature
      Added value: +{
+  "description": "Optional base64 x402 v2 PAYMENT-SIGNATURE header generated by an authorised payer for the exact resource returned by an unpaid call. Omit to request a challenge. This is a payment payload, never a seed, private key, or password.",
+  "maxLength": 16384,
+  "minLength": 4,
+  "pattern": "^[A-Za-z0-9+/]+={0,2}$",
+  "type": "string"
+}
    • addedInput schema / properties / side / description
      Added value: +"Trade direction: buy spends AUD to acquire the asset; sell quotes disposal into AUD. Defaults to buy."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: it discloses that results are estimates rather than executable quotes, that no trade is placed, that this is a paid XRP/XRPL data-access tool, and details the x402 v2 payment handshake (challenge on first call, PAYMENT-SIGNATURE retry with identical inputs, no wallet secrets, verify settlement before retrying). This is far beyond anything structured fields provide.

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?

Purpose and the sibling routing are front-loaded in the first two sentences, followed by the payment mechanics. The payment paragraph is long but each sentence is actionable for a paid tool; only slight tightening is possible.

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?

With no annotations and no output schema, the description covers the essential behavioral picture (estimate semantics, no trade, payment flow) and gestures at the return ('estimated value received'). It could say slightly more about the comparison output shape, but nothing an agent needs to invoke it correctly is missing.

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%, so asset, amount, side, and paymentSignature are already fully documented in the schema with defaults and constraints. The description restates the asset/amount/direction framing but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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 (compare) and resource (Australian cryptocurrency exchanges) with scope: best estimated buying or selling outcome for a given asset, AUD amount, and direction. It explicitly names and distinguishes itself from the sibling find_where_to_buy_crypto, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('when the user wants to compare exchange prices, fees or estimated value received') and an explicit alternative with its selecting condition ('For simply finding exchanges that offer a cryptocurrency, use find_where_to_buy_crypto instead'). Both routing and usage context are covered.

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

All CryptoBuddy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources