Skip to main content
Glama

X1 holder overlap

x1_holder_overlap
Read-onlyIdempotent

Analyze shared top holders and wallet overlap across 2 or 3 X1 token mints (base58). $0.003 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_holder_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintsYes2 or 3 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.2/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds the two things an agent most needs and cannot get from annotations: a concrete price ($0.003 per call) and the accepted payment rails (USDC on Arc, Base or Solana, or XNT on X1). It also discloses that the purchase settles inside the tool call itself, which is a real side effect an agent must anticipate.

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 sentences, both load-bearing: the first defines the analysis and its input constraint, the second defines cost and the call sequence. No filler, and the analytical scope is front-loaded before the payment mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 says nothing about what the analysis returns — shared-holder counts, overlap percentages, wallet lists, or per-mint breakdowns — which matters for an analytics tool whose value is the result shape. Payment, cost, and input constraints are fully covered, so the gap is confined to return-value expectations.

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 the baseline is 3; the description still adds meaning by explaining the two-step role of `payment` (first call returns terms, second call with a signed payload completes the purchase), which the schema only hints at. It restates the base58/2-or-3 constraint on `mints` rather than extending it.

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?

States a specific verb and resource ('Analyze shared top holders and wallet overlap') plus a hard scope constraint ('across 2 or 3 X1 token mints'), so an agent knows exactly what computation is being bought. It does not name or contrast any sibling such as x1_token_compare or x1_wallet_holdings, so the differentiation is left implicit.

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 usage protocol is spelled out precisely: call once without `payment` to get terms, sign them with your own wallet, then call again with `payment`. That removes the main failure mode for x402 tools. It gives no guidance on when to prefer this over neighboring analytics tools, which is the only missing piece.

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