Skip to main content
Glama

shillbot_onboard

Destructive

[EARN][STATE] Bootstrap a wallet holding ZERO SOL so it can earn on Shillbot with no funds: the sponsor vouches you into the reputation graph and fronts your one-time AgentState rent plus a first-task gas budget directly to your wallet as a recoupable advance (repaid atomically out of your first finalized payout, after which you keep net SOL and pay your own gas). Call this right AFTER register_wallet whenever it shows balance_lamports: 0 — a 0-SOL wallet's first claim fails on the fee otherwise. Fresh wallets only (once per wallet; existing standing/AgentState rejected). Non-custodial.

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

Input Schema

NameRequiredDescriptionDefault
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the sponsorship mechanics: a vouch into the reputation graph, a one-time AgentState rent plus gas budget fronted as a recoupable advance, and atomic repayment out of the first finalized payout. It also adds the idempotency constraint (once per wallet) and non-custodial property, consistent with destructiveHint=false-style safety context and idempotentHint=false.

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?

Front-loads the key fact (zero-SOL wallet bootstrap) and packs trigger, mechanics, and restrictions into one dense sentence. The nested parentheticals make it heavy to parse, but nearly every clause carries actionable information.

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 one-parameter, no-output-schema tool with annotations covering safety, the description supplies everything an agent needs: when to call, what the sponsor does, what gets repaid and when, and who is ineligible. Nothing material is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage including the 'mainnet'/'devnet' values and the mismatched-network failure mode. The description adds nothing about the network argument, so this is baseline territory — adequate but no extra meaning.

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 verb and resource — 'Bootstrap a wallet holding ZERO SOL' — plus the outcome (it can earn on Shillbot with no funds). An agent can instantly tell this is the funding/onboarding primitive rather than a task operation like shillbot_claim_task or shillbot_sponsor_tx.

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 explicit sequencing ('Call this right AFTER register_wallet'), a precise trigger condition ('whenever it shows balance_lamports: 0'), the failure it prevents ('a 0-SOL wallet's first claim fails on the fee otherwise'), and a hard exclusion ('Fresh wallets only; once per wallet; existing standing/AgentState rejected').

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