Skip to main content
Glama

X1 search

x1_search
Read-onlyIdempotent

Search X1 tokens by name, symbol or mint address (up to 10 matches). $0.002 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": {
      "q": "<q>"
    },
    "name": "x1_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYestoken name, symbol, or mint
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

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: a per-call price of $0.002, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step handshake. It still omits error/failure behavior and what the terms payload looks like, so it is strong but not exhaustive.

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, no padding: capability and scope first, pricing and the required call sequence second. Every clause carries information an agent needs before invoking it.

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 only two parameters and no output schema, the definition covers what it must: scope, cost, payment rails, and the mandatory two-call flow, plus a hint at result volume ('up to 10 matches'). It leaves the shape of the first-call terms response unstated, which is the main residual gap for a paid 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 text already documents both parameters, so the baseline is 3. The description goes further by explaining the temporal semantics of `payment` — omitting it yields terms, supplying it completes the purchase in the same call — which is meaning the schema alone does not convey.

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 ('Search X1 tokens') plus the searchable fields (name, symbol, mint address) and a result cap of 10 matches. It does not explicitly distinguish itself from adjacent search/report siblings such as x1_token_report or market_search, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear procedural path (call once without payment to get terms, sign, call again with payment), which is useful invocation guidance. However, it never says when to choose this over the other search tools in the catalog, nor what to do if no matches or the payment fails.

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