Skip to main content
Glama

shillbot_verify_task

Destructive

[EARN: SOL] Build an oracle-co-signed verify_task tx (your wallet as fee payer) after the verifier scores a task (~5m for game/website, 7d for YouTube/X). Sign locally and broadcast via shillbot_submit_tx action="verify".

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

Input Schema

NameRequiredDescriptionDefault
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
task_idYesThe task identifier (format: `<campaign_id>:<task_uuid>`) of the submitted task to verify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is covered. The description adds genuinely new context: the caller's wallet pays fees, the tx is oracle-co-signed, signing happens locally, and there are multi-day latency windows. It omits what happens on a failed or rejected verification, which is the main remaining behavioral gap.

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 action and precondition front-loaded and the handoff to the broadcast tool at the end. The bracketed "[EARN: SOL]" tag and parenthetical timings are compact and informative rather than filler.

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 two-parameter mutation tool with no output schema, the description covers cost, signing model, latency, and the next step, which is most of what an agent needs. It leaves out failure/retry behavior and how to confirm the verifier has actually scored the task.

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 both task_id (with its `<campaign_id>:<task_uuid>` format) and network are already documented in the schema. The description adds no parameter-level detail beyond that, so the baseline 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?

States a specific verb and resource ("Build an oracle-co-signed verify_task tx") plus the precondition (after the verifier scores a task) and the fee-payer role. It also names the sibling that performs the next step (shillbot_submit_tx action="verify"), so an agent can place it in the workflow without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear trigger condition and timing expectations (~5m for game/website, 7d for YouTube/X) and explicitly routes the follow-up to shillbot_submit_tx with action="verify". It does not state what to do if verification fails or how to check whether the verifier has scored yet, so it stops short of full when/when-not guidance.

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