Skip to main content
Glama

shillbot_submit_work

Destructive

[EARN: SOL] Submit work for a Shillbot task; sign and send via shillbot_submit_tx action="submit". content_id by platform: 11=::[:sig:<b64url_or_0xhex>] (atomic claim+submit on Open task, ~1m); 10=lean4:proof:, HTTPS .lean URL, or pass raw source in proof_lean (~5m); 5=game_id (~5m); 4=campaign_id (~5m); 9=page URL (~5m); 0/3=video/tweet ID (T+7d).

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_submit_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
task_idYesTask ID (`<campaign_id>:<task_uuid>`).
content_idNoWork proof ID (video/tweet ID, game_id, URL, or `<caip2>:<tx>:<idx>[:sig:<sig>]`). Optional if `proof_lean` is set.
proof_leanNoLeanProof (10): raw `.lean` source (`content_id` optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / content_id / default
      Added value: +""
    • changedInput schema / properties / content_id / description
      Previous value: -"The content ID of the completed work (YouTube video ID, tweet ID,\ngame session ID, etc.)."New value: +"Work proof ID (video/tweet ID, game_id, URL, or `<caip2>:<tx>:<idx>[:sig:<sig>]`). Optional if `proof_lean` is set."
    • addedInput schema / properties / proof_lean
      Added value: +{
      +  "description": "LeanProof (10): raw `.lean` source (`content_id` optional).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / task_id / description
      Previous value: -"The unique task identifier (format: `<campaign_id>:<task_uuid>`)."New value: +"Task ID (`<campaign_id>:<task_uuid>`)."
    • changedInput schema / required
      Previous value: -[
      -  "task_id",
      -  "content_id"
      -]New value: +[
      +  "task_id"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent, non-read-only, so the risk profile is known. The description adds real behavioral context not in the annotations: an 'atomic claim+submit on Open task' and per-platform timing (~1m, ~5m, T+7d). It does not explain that the on-chain send is irreversible, what happens if it fails, or what it returns, which matters given the destructive hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The earn tag and core instruction are front-loaded, but the remainder is a single dense semicolon chain that mixes submission routing, proof encodings, and timing without structure. A short bulleted or labelled form for the per-platform formats would cost little space and read far faster.

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?

No output schema exists, so the description should say what comes back (a signed submission, an attestation, a task state change), and it does not. For a destructive, open-world mutation with a companion transaction tool, the ambiguity over whether this tool itself broadcasts on-chain is a meaningful gap.

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 goes further by decoding content_id formats per platform (11=<caip2>:<tx>:<idx>[:sig:...], 10=lean4:proof/URL/raw source, 5=game_id, 4=campaign_id, 9=page URL, 0/3=video/tweet ID), which the schema does not describe. The numeric platform codes are never defined, so some of the mapping remains opaque.

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 ('Submit work for a Shillbot task') and names the sibling shillbot_submit_tx with the action='submit' routing, so an agent can tell it apart from the raw transaction tool. The purpose is further scoped by the '[EARN: SOL]' tag and per-platform proof formats, though the exact boundary between 'submit work' here and 'submit_tx' there is left slightly implicit.

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?

It names the companion path ('sign and send via shillbot_submit_tx action="submit"') and gives per-platform proof inputs and expected confirmation windows, which is genuine usage guidance. It never states prerequisites such as having claimed the task, nor when to prefer complete_task/verify_task over this, so usage is implied rather than explicit.

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