Skip to main content
Glama

xchain_supported_chains

Read-onlyIdempotent

[READ] List the chains a cross-chain Coordination Game match can run on: CAIP-2 id, native coin, per-match stake, tranche clamp, claim window, contract address, plus a plain-language staking/settlement model. Live on Mainnet (Solana, Base, Ethereum — prefer Base over Ethereum L1, as L1 gas can exceed the ~$5 stake) and Testnet (Solana Devnet, Base Sepolia). Call BEFORE register_wallet to choose Solana (base58) vs EVM (0x). No wallet required.

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": "xchain_supported_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add operational context—and it does: no wallet needed, Mainnet vs Testnet coverage with named networks, and a real economic constraint (L1 gas vs the ~$5 stake) that shapes which chain to pick. It stops short of describing pagination, caching, or freshness of the returned chain data, 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?

Leads with the '[READ]' tag and the core purpose, then layers the return fields, network availability, and a call-order directive as separate clauses. Dense but every clause carries information an agent acts on—nothing is padding.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with no output schema, the description covers the full decision surface: what is returned, which networks are live, which to prefer and why, and that it must run before register_wallet. An agent could invoke and interpret it correctly without any other source.

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?

The tool takes zero parameters, so the schema imposes nothing to explain and the baseline is 4. The description instead spends its words on the response payload's fields, which is useful because no output schema exists to document them.

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?

Names a specific verb and resource ('List the chains a cross-chain Coordination Game match can run on') and enumerates exactly what each entry contains: CAIP-2 id, native coin, stake, tranche clamp, claim window, contract address, and a staking/settlement model. The '[READ]' prefix plus the explicit return-field list distinguishes it from every sibling, which are build/sign/status tools.

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

Usage Guidelines5/5

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

Gives an explicit sequencing instruction—'Call BEFORE register_wallet to choose Solana (base58) vs EVM (0x)'—so the agent knows both when to call it and what decision it feeds. It also supplies a selection rule among results ('prefer Base over Ethereum L1, as L1 gas can exceed the ~$5 stake') and states 'No wallet required', which removes any prerequisite doubt.

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