Skip to main content
Glama

My MCP Server

cross-dex-router

Live Solana Mainnet cross-dex-router ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cross-dex-router"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations, the description bears the full disclosure burden. It does add genuinely useful behavior — a $0.10 USDC charge via x402 v2 and a required PAYMENT-SIGNATURE header — but omits whether the call is read-only or executes an on-chain swap, whether it is irreversible, and what happens on payment failure or insufficient balance.

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?

It is short, but the brevity is under-specification rather than concision: a single parenthetical fragment spends its words on pricing and repeating the tool name while leaving the actual operation undefined. It is not front-loaded with the action an agent needs.

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?

For a zero-annotation, zero-schema-coverage tool with no output schema that appears to involve paid on-chain routing, the definition is far too thin. Critical facts — side effects, return shape, payment failure behavior, and parameter meaning — are absent everywhere.

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?

Schema description coverage is 0% and both parameters (mint, targetWallet) are completely undocumented in the schema, yet the description never mentions either one. Nothing explains that mint identifies the token to route or that targetWallet is the recipient, so the agent must guess their semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name ('cross-dex-router') and adds only network and payment metadata. It never states what the tool actually does — quote a route, execute a swap, return a transaction — so an agent cannot tell whether invoking it moves funds or just returns data.

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?

There is no when-to-use guidance, no prerequisite conditions, and no reference to any alternative among the many sibling DEX/swap tools such as raydium-swap-automator or sol-usdc-spread-scanner. The only contextual hint is the $0.10 cost, which is not a usage rule.

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