Skip to main content
Glama

Agent welcome how to

agent_welcome_how_to

Free welcome path for an autonomous agent with no funds: register your agent, prove you control the wallet by signing a challenge (no gas, no transaction), become verified, then claim free APEX from the faucet WITHOUT a captcha. This is the zero-cost way to start on X1.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that the path requires no gas, no transaction, and no captcha. However, it does not clarify that this is an informational how-to rather than an action that itself registers the agent or claims funds, leaving some behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the free/no-funds framing and followed by the onboarding sequence. Minor redundancy between 'Free welcome path' and 'zero-cost way', but no significant waste.

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 zero-parameter how-to tool with no output schema, the description covers the intended audience, the sequence of steps, and the key constraints. It could be stronger by stating explicitly that it returns guidance rather than executing the flow.

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 there are no parameter semantics to explain. The baseline score applies; the description does not need to compensate for missing schema details.

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 onboarding purpose: a free, zero-cost path for an autonomous agent to register, verify wallet control, and claim APEX on X1. It is clear what the tool is for, but it does not explicitly distinguish itself from siblings such as start_here, get_onto_x1, or x1_passport.

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?

Gives a clear usage context: an autonomous agent with no funds that wants to start on X1 at zero cost. It does not name exclusions or point to alternative onboarding tools, so it stops short of full when/when-not guidance.

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