Skip to main content
Glama

shillbot_sponsor_tx

[EARN][STATE] Devnet two-step gas sponsorship for a locally built claim or submit tx (retired on mainnet: shillbot_onboard fronts your first-task gas budget directly via open_advance so you self-pay as fee payer). Omit unsigned_transaction first to get the template, then submit unsigned_transaction for the fee-payer signature.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "action": "<action>"
    },
    "name": "shillbot_sponsor_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesSponsorship is deliberately limited to "claim" or "submit".
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
task_idYesThe task identifier for the locally constructed transaction.
content_idNoRequired when requesting a submit sponsorship template; it must match the content id encoded in the locally constructed transaction.
unsigned_transactionNoBase64 unsigned transaction constructed locally. Omit on the first call to receive the sponsor fee payer and any required payout route; pass it on the second call for complete validation and co-signing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already identify this as a non-read-only, non-idempotent, open-world operation. The description adds useful behavioral context beyond those annotations: devnet-only availability, the two-step template/signature flow, and the mainnet retirement path through shillbot_onboard. It does not cover error behavior or repeated-call semantics, but the core behavioral model is well disclosed.

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?

The description is front-loaded with the main purpose, then adds the mainnet caveat and two-step instructions. It is compact for the amount of workflow information conveyed, though the bracketed tags and parenthetical mainnet explanation make it slightly dense.

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 five-parameter stateful sponsorship tool with no output schema, the description covers the key workflow, network restriction, and mainnet alternative. It explains what the first call returns at a high level, though it could say more about the second call's result or failure modes.

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?

Schema description coverage is 100%, so the schema already documents all five parameters, including the two-step use of unsigned_transaction and the action restriction to claim or submit. The description reinforces the unsigned_transaction workflow but adds little parameter meaning beyond what the schema already provides, making the baseline score appropriate.

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 states a specific resource and operation: devnet two-step gas sponsorship for a locally built claim or submit transaction. It explicitly distinguishes the supported action types and calls out that the tool is retired on mainnet in favor of shillbot_onboard, so an agent can identify its scope without opening the schema.

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 gives explicit sequencing instructions: omit unsigned_transaction on the first call, then pass it on the second call for fee-payer co-signing. It also names the mainnet alternative and explains that shillbot_onboard covers first-task gas there, leaving little ambiguity about when to use this tool.

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