Skip to main content
Glama

shillbot_submit_tx

Destructive

[STATE] Broadcast a signed Shillbot Solana tx (create, claim, submit, approve, verify, finalize, expire) after validating its program, action, accounts, signers, movements, fee payer, network, and signatures. action="create" spends the displayed amount into escrow. Supports self-paid txs and devnet gas-sponsored claim/submit txs.

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>",
      "signed_transaction": "<signed_transaction>"
    },
    "name": "shillbot_submit_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction matching the builder tool: "create" | "claim" | "submit" | "approve" | "verify" | "finalize" | "expire".
networkNo"mainnet" (default) or "devnet" — must match the unsigned tx cluster.
task_idYesTask ID the signed tx applies to.
task_pdaNoBase58 Task PDA (required for action="create"; ignored otherwise).
signed_transactionYesBase64 locally-signed Solana transaction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"One of \"create\", \"claim\", \"submit\", \"approve\", \"verify\", \"finalize\" —\nmatching the build tool that produced the unsigned tx."New value: +"Action matching the builder tool: \"create\" | \"claim\" | \"submit\" | \"approve\" | \"verify\" | \"finalize\" | \"expire\"."
    • changedInput schema / properties / network / description
      Previous value: -"\"mainnet\" (default) or \"devnet\" — must match the network the unsigned\ntx was built on, or the broadcast lands on the wrong cluster."New value: +"\"mainnet\" (default) or \"devnet\" — must match the unsigned tx cluster."
    • changedInput schema / properties / signed_transaction / description
      Previous value: -"Base64 signed Solana transaction (built by the matching tool, signed\nlocally)."New value: +"Base64 locally-signed Solana transaction."
    • changedInput schema / properties / task_id / description
      Previous value: -"The task identifier the signed tx applies to."New value: +"Task ID the signed tx applies to."
    • changedInput schema / properties / task_pda / description
      Previous value: -"On-chain Task PDA (base58). REQUIRED for action=\"create\" (pass back\nshillbot_create_campaign's task_pda); ignored otherwise."New value: +"Base58 Task PDA (required for action=\"create\"; ignored otherwise)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the validation checklist performed before broadcast, the fact that action="create" moves the displayed amount into escrow, and which flows can be gas-sponsored on devnet. It does not state what happens on validation failure or what the call returns.

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 dense sentences with the core operation front-loaded after the [STATE] tag, and no filler phrasing. The long validation list is informative rather than wasteful, though it makes the first sentence heavy enough to require a second read.

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 five fully documented parameters, rich annotations, and no output schema, the description covers enough for correct invocation: what it does, the preconditions it checks, and the special escrow and sponsorship cases. The main remaining gap is that it never indicates what the caller gets back (e.g., a signature or confirmation status), which matters for a broadcast operation lacking an output schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that action="create" causes the displayed amount to be spent into escrow and that network must match the unsigned tx cluster for sponsored devnet claim/submit flows. This is genuine semantic value rather than a restatement of field names.

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?

The description uses a specific verb ('Broadcast') plus a precise resource ('a signed Shillbot Solana tx') and enumerates the seven action types it covers, so the agent knows exactly what this tool does. It implicitly separates itself from the builder/confirmation siblings by requiring an already-signed transaction, but never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the ordering constraint ('after validating its program, action, accounts...') and the note that it supports self-paid txs and devnet gas-sponsored claim/submit txs. There is no explicit when-to-use vs. when-not guidance and no routing to siblings such as shillbot_confirm_tx or shillbot_sponsor_tx, leaving the agent to infer the workflow position.

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