Skip to main content
Glama

X1 spread scan

x1_spread_scan
Read-onlyIdempotent

Cross-pool X1 DEX spread & depth scanner across XDEX, APEX AMM and COMMODITY pools: refreshes live XDEX vaults, excludes blacklisted tokens, and simulates net-of-fee round trips at 1, 3 and 5 XNT. Not advice. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "x1_spread_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNooptional X1 token mint (base58)
min_liqNominimum pool XNT liquidity (default 10)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
trade_xntNoXNT trade size (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the refresh behavior (live XDEX vaults), a filtering rule (blacklisted tokens excluded), the simulation set (1, 3, 5 XNT), and a concrete cost model ($0.004/call, accepted assets and chains). One tension worth noting: annotations say readOnlyHint=true while the description says a payment purchase completes inside the call, though the description is transparent about it so the agent is not misled about cost.

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?

The core capability is front-loaded in the first clause, followed by behavior, cost, and the call procedure in a compact sequence. The 'Not advice' disclaimer and repeated payment phrasing cost a little space but each sentence carries operational content.

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?

For a paid, multi-pool scanner with no output schema, the definition covers what is scanned, what is excluded, what is simulated, what it costs, and the exact invocation sequence. Nothing an agent needs in order to call it correctly is absent.

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 coverage is 100%, so all four parameters are already documented, making 3 the baseline. The description adds real meaning only for `payment`, explaining the two-step terms-then-signed-payload flow; it does not clarify `mint` (all tokens if omitted?) or reconcile the '1, 3 and 5 XNT' simulation sizes with the single `trade_xnt` parameter.

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 names a specific verb+resource+scope: a cross-pool spread and depth scanner over XDEX, APEX AMM and COMMODITY pools, including the concrete computation performed (net-of-fee round trips). An agent can distinguish this from neighbors like x1_pool_health or x1_token_compare without opening the schema.

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 paid-access procedure is spelled out precisely: call once without `payment` to get terms, sign with your own wallet, call again with `payment` to complete. That is strong when-to-call-this-way guidance. What is missing is routing guidance versus sibling analysis tools (pool health, token compare) for an agent that just wants spread data without paying.

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