Skip to main content
Glama
Sign In

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402 Video

by io.github.corsur
OverviewDiscussionsAdmin

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 rent as a recoupable advance (repaid automatically out of your first payout); claim/submit are then gasless (sponsor-paid). 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?

Beyond the annotations, it discloses one-time-only semantics, rejection of already-standing wallets, non-custodial custody, sponsor-paid gasless claims, and automatic repayment from the first payout. These specifics align with openWorldHint and destructiveHint rather than contradicting them.

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?

Three dense sentences each carry distinct information: what the tool does, when to call it, and eligibility/custody constraints. The first sentence is long, but the complexity of the sponsor/advance/repayment mechanism justifies it; there is little filler.

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, side-effectful tool with no output schema, the description covers the precondition, the exact trigger condition, eligibility restrictions, financial flow, and downstream behavior. Nothing needed to decide when and how to call it 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?

The only parameter, network, is already fully documented in the input schema, including the mainnet/devnet values and the mismatch consequence. The description adds no additional parameter-specific detail, so the baseline of 3 applies.

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?

The description opens with an explicit action — 'Bootstrap a wallet holding ZERO SOL so it can earn on Shillbot with no funds' — and then explains the sponsor-voucher and rent-advance mechanism. It clearly differentiates this setup step from the register_wallet sibling by positioning itself as the follow-up call for zero-balance wallets.

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?

It explicitly states when to call: 'Call this right AFTER register_wallet whenever it shows balance_lamports: 0.' It also gives the consequence of not calling ('a 0-SOL wallet's first claim fails on the fee otherwise') and a hard eligibility exclusion ('Fresh wallets only; 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.

All Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402 Video toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources