Skip to main content
Glama

Diogenes Web3, DeFi & 402 Security MCP

Non-KYC Cross-Chain Bridge Route & Settlement Fee Comparator

compare_crosschain_bridge_routes
Read-onlyIdempotent

Compares non-custodial, non-KYC cross-chain swap routes (THORChain native L1 swaps, Maya Protocol, Blockstream Liquid) by basis-point fee, net output sats, and settlement time. Use when routing cross-chain treasury settlements (e.g. Solana USDC or Base ETH into native Bitcoin); for calculating mid-market spot exchange rates without bridge routing fees, use calculate_spot_swap_rate instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'from_asset' ('to_asset' defaults to 'BTC_NATIVE'), supports '?demo=true' or L402 (20 sats), and returns HTTP 400 if invalid.

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": {
      "from_asset": "<from_asset>"
    },
    "name": "compare_crosschain_bridge_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoInput asset amount to quote; defaults to 100.0 when omitted.
to_assetNoDestination chain asset identifier; defaults to 'BTC_NATIVE' when omitted.
from_assetYesOrigin chain asset identifier to bridge from.

Output Schema

NameRequiredDescriptionDefault
fee_bpsYesTotal protocol and slip fee in basis points.
best_routeYesOptimal non-KYC bridge protocol selected (e.g. 'THORCHAIN_NATIVE_SWAP').
kyc_requiredYesAlways false; only non-custodial permissionless routes are returned.
estimated_output_satsYesNet settled output denominated in Bitcoin satoshis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, and the description adds substantial context beyond that: stateless edge call, 32 KB max, 60 RPM limit, demo mode or L402 payment (20 sats), and HTTP 400 on invalid input. It also clarifies that from_asset is the required input and to_asset defaults to BTC_NATIVE.

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 wasted words. The comparison scope and differentiator are front-loaded ahead of operational details, so the agent gets the key routing decision first.

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?

Given an output schema, 100% parameter coverage, and rich annotations, the description fills the remaining gaps: target use case, alternative tool, access/payment model, rate limits, and error behavior. Nothing an agent needs to select or 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 the baseline is 3 even with no parameter detail in the description. The description does mention from_asset and to_asset defaults, but that information duplicates what the schema already documents; it does not add new semantics such as amount formatting or enum constraints.

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 ('Compares') plus the exact resource (non-KYC cross-chain swap routes across THORChain, Maya, and Liquid) and the metrics compared (bp fee, net output sats, settlement time). It also explicitly distinguishes itself from the sibling calculate_spot_swap_rate, so an agent can tell them apart 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 Guidelines5/5

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

Gives an explicit use case ('routing cross-chain treasury settlements, e.g. Solana USDC or Base ETH into native Bitcoin') and names the alternative tool with the condition that selects it ('for calculating mid-market spot exchange rates without bridge routing fees, use calculate_spot_swap_rate instead'). Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.