Skip to main content
Glama

shillbot_confirm_tx

Destructive

[STATE] Confirm a Shillbot transaction you constructed and broadcast through your own RPC. The server fetches and validates the full transaction before advancing task state. Supports create, claim, submit, approve, verify, finalize, and expire; create escrows the campaign amount.

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>",
      "tx_signature": "<tx_signature>"
    },
    "name": "shillbot_confirm_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesOne of create, claim, submit, approve, verify, finalize, or expire.
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
task_idYesThe task identifier the already-broadcast transaction applies to.
task_pdaNoRequired for create; ignored for other actions.
tx_signatureYesBase58 Solana signature returned by the caller's own RPC broadcaster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"One of create, claim, submit, approve, verify, or finalize."New value: +"One of create, claim, submit, approve, verify, finalize, or expire."
  2. First observed

TDQS

A3.6/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; the description adds real context beyond that: the server re-fetches and validates the transaction before advancing state, and create escrows the campaign amount. It still doesn't say what happens on validation failure or whether a failed confirm can be retried.

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 sentences, front-loaded with the confirm action and its precondition, then behavior, then the action list. The bracketed '[STATE]' prefix is slightly obscure, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive state-advancing tool with no output schema, the description covers purpose and validation behavior but says nothing about the response, failure modes, or idempotency expectations. Adequate to call correctly, thin on what to expect back.

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 coverage is 100%, so the schema already documents task_id, tx_signature, network, task_pda, and action. The description reinforces the action set and notes that create escrows funds, but adds no format or edge-case detail (e.g., task_pda being create-only) beyond what the schema already states.

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 verb and resource: 'Confirm a Shillbot transaction you constructed and broadcast through your own RPC.' That framing distinguishes the tool from server-side broadcast siblings, though it never names shillbot_submit_tx or shillbot_sponsor_tx directly, so the agent must infer the division of labor.

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?

The phrase 'broadcast through your own RPC' implies the precondition for using this tool, and the action list implies it covers the whole lifecycle. But there is no explicit when-not guidance or named alternative for callers who have not yet broadcast, leaving the choice between this and submit/sponsor tools implicit.

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