Skip to main content
Glama

Get onto x1

get_onto_x1

How to get onto the X1 chain and fund a wallet with APEX/XNT from outside — bridge from Solana (USDC or SOL), or claim free tokens from the faucet. Returns the real bridge deposit address, limits and endpoints. Start here if you have no X1 balance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the tool is informational and that it 'Returns the real bridge deposit address, limits and endpoints' — the 'real' qualifier usefully warns against fabricated addresses. It does not state whether it also executes a bridge or faucet claim, though the lack of parameters implies it does not.

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?

Three short sentences ordered purpose → alternatives → return value → entry condition, with zero padding. The most decision-relevant information (what chain, what funding routes) is front-loaded.

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 annotations, no output schema, and no parameters, the description must explain both what is returned and when to call it, and it does both (deposit address, limits, endpoints; 'start here if you have no X1 balance'). Minor gaps remain around whether the faucet route has eligibility limits or whether the returned endpoints are chain-specific, but nothing blocks a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline expectation is already met by the empty schema. The description adds only indirect param guidance by enumerating the inputs a user would need (Solana USDC/SOL), not by documenting arguments.

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?

States a specific action and resource: 'How to get onto the X1 chain and fund a wallet with APEX/XNT from outside', naming both mechanisms (Solana bridge with USDC or SOL, faucet claim). The chain name X1 distinguishes it from the sibling get_onto_arc, so an agent can route between the two 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?

'Start here if you have no X1 balance' is an explicit entry condition, and the description separates the two paths (bridge vs. faucet) by holder situation. It stops short of a when-not case, e.g. what to use once a balance exists (x1_agents, x1_passport), so it is clear but not exhaustive.

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