Skip to main content
Glama

transfer route

transfer-route
Read-onlyIdempotent

Cheapest open network to move a coin from exchange A to exchange B: withdraw/deposit open, fee, minimums, memo, ETA, congestion; same-ticker-different-contract traps flagged Price: $0.05 per call, USDC on Base via x402.

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": {
      "coin": "<coin>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "transfer-route"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesbitget|gate|htx|kucoin
coinYesstring, e.g. USDT (default USDT)
fromYesbitget|gate|htx|kucoin
amountNonumber (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: the per-call price ($0.05), the x402/USDC-on-Base payment mechanism, and the fact that same-ticker-different-contract traps are flagged — all relevant behavior an agent cannot get from annotations.

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 dense clause list front-loads the core purpose, then the returned attributes, then cost. It is compact and earns nearly every token, though the pricing sentence is jammed against the previous clause without a separator, slightly hurting scanability.

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 output schema, the description usefully enumerates what comes back (withdraw/deposit status, fee, minimums, memo, ETA, congestion, contract traps). What is missing is edge behavior — what happens when no open route exists, and whether 'cheapest' optimizes network fee alone or fee plus withdrawal/deposit charges.

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% and the exchange enum values are already listed in the schema, so the baseline of 3 applies. The description hints that coin identity is contract-aware ('same-ticker-different-contract traps') which slightly enriches the coin parameter, but it says nothing about what amount changes (route ranking vs. minimum checks).

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 names a specific verb and resource plus scope: finding the cheapest open network to move a coin between two named exchanges. It is not tautological with the title 'transfer route', but it never explicitly contrasts itself with adjacent tools like ticker-collision or token-check, leaving sibling differentiation to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for planning an exchange-to-exchange transfer. There is no statement of when not to use it (e.g., same-exchange moves, unsupported exchanges) and no named alternative for related questions.

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.

Resources