Skip to main content
Glama

X1 token report

x1_token_report
Read-onlyIdempotent

Comprehensive X1 token safety report: price, liquidity, burned LP %, holders, authorities, exit ladder and verdict. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, sign 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": {
      "mint": "<mint>"
    },
    "name": "x1_token_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesX1 token mint address (base58)
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing cost ($0.01 per call), accepted payment rails (USDC on Arc, Base or Solana, or XNT on X1), and the mandatory two-call x402 handshake. That payment gating is the single most important behavioral fact for an agent and it is stated plainly.

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, front-loaded with what the report delivers and then the payment mechanics. No filler, no restatement of the title, and the most decision-relevant fact (cost and payment flow) comes before any invocation detail.

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 compensates by enumerating the report's field categories, and the payment flow and price are fully specified. It stops short of describing the response structure, error/unpaid-challenge behavior, or freshness of the token data, which are the remaining unknowns for a paid read tool.

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 earns extra credit by explaining the role of the optional `payment` parameter in the challenge/sign/submit cycle rather than just naming it. The required `mint` parameter's meaning and base58 format are left entirely to the schema.

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 resource (X1 token) and enumerates exactly what the report contains: price, liquidity, burned LP %, holders, authorities, exit ladder and verdict. The X1 chain qualifier plus the '.01 per call' framing lets an agent distinguish it from siblings like solana_token_report or arc_token_check without opening a 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?

It gives a precise invocation sequence: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. That is explicit operational guidance, but it never states when this tool is preferable to a sibling such as x1_wallet_report or the generic token_lookup, nor any exclusion conditions.

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