Skip to main content
Glama

X1 agent board

x1_agent_board
Read-onlyIdempotent

X1 on-chain AI agent leaderboard: registered agents, capabilities, verified endpoints, and activity metrics. $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

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_agent_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many agents to return, 1 to 50 (default 20)
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 establish read-only, open-world, idempotent, and non-destructive behavior. The description adds important context beyond that: the tool costs $0.002 per call, uses x402 payments over several rails, and requires a two-step terms-signing flow. It does not cover rate limits, pagination behavior, or what the first no-payment call returns in detail.

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?

The description is two sentences and front-loads what the tool provides before explaining cost and payment mechanics. Every sentence carries useful information, with no redundant restatement of the tool name or schema fields.

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?

For a paid data-retrieval tool with two parameters and no output schema, the description explains the content scope, pricing, and payment invocation flow well enough to call it correctly. It could be more complete by clarifying what the first no-payment call returns and how results are shaped after payment, but the core invocation details are present.

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 `limit` and `payment` parameters are already documented structurally. The description adds meaning by explaining that `payment` is part of a two-call x402 flow where the first call returns terms and the second call completes the purchase. It does not add details about `limit`, but the schema handles that.

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 clearly identifies the tool as an X1 on-chain AI agent leaderboard and lists the kinds of data it exposes: registered agents, capabilities, verified endpoints, and activity metrics. It does not explicitly differentiate this leaderboard from nearby tools such as x1_agents or arc_agent_search, so it falls 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?

The description gives detailed guidance for the x402 payment workflow: call once without payment for terms, sign them, then call again with payment. However, it does not say when an agent should choose this leaderboard tool over siblings like x1_agents or arc_agent_search, so alternative-selection guidance is only implied.

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