Skip to main content
Glama

X1 token compare

x1_token_compare
Read-onlyIdempotent

Side-by-side comparison of 2 to 5 X1 token mints: liquidity, price, holders, and pool health. $0.005 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

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": {
      "mints": "<mints>"
    },
    "name": "x1_token_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintsYes2 to 5 comma-separated X1 token mints (base58)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnly/idempotent/non-destructive/openWorld; the description adds pricing ($0.005 per call), accepted payment rails (USDC on Arc, Base, Solana, or XNT on X1), and the two-phase settlement protocol — material behavior an agent cannot infer from annotations. The settlement of a payment inside a call marked readOnlyHint=true is a mild tension, but it is fully disclosed rather than hidden.

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?

Three sentences, front-loaded with what is compared, followed by cost and then the call protocol; nothing is redundant. The middle sentence is dense with rail/pricing detail but every element is actionable for an agent deciding whether it can pay.

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?

There is no output schema, and the description names the comparison dimensions but not the return shape (per-token rows vs. a comparative matrix), and it says nothing about failure modes such as fewer than 2 mints or a rejected payment. For a two-parameter read tool those are modest gaps against otherwise thorough behavioral disclosure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented structurally. The description goes beyond that by explaining the protocol semantics of `payment` — first call yields terms, you sign them, second call with the signed payload completes the purchase in-call — which is genuine meaning the schema field text only partially conveys.

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 gives a specific verb and resource ('side-by-side comparison of 2 to 5 X1 token mints') and enumerates the compared dimensions: liquidity, price, holders, pool health. That scope statement implicitly distinguishes it from single-token siblings like x1_token_report or x1_pool_health, though it never names an alternative explicitly.

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?

Usage guidance is strong on the mechanics that matter: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment` to complete the purchase. It gives no guidance on when to prefer this over a single-token report or a dedicated pool-health tool, so it is clear context without exclusions.

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