Skip to main content
Glama

shillbot_finalize_task

Destructive

[EARN: SOL] Settle a task: mode="finalize" (default, pays agent post-challenge and recoups any advance) or mode="expire" (client escrow refund past deadline or submitted_at + verification_timeout if unverified). Sign locally and submit via shillbot_submit_tx.

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

Input Schema

NameRequiredDescriptionDefault
modeNo`"finalize"` (default, post-challenge payout) or `"expire"` (client escrow refund past claim/submit deadline or past `submitted_at + verification_timeout` if never self-verified).
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
task_idYesTask ID (`<campaign_id>:<task_uuid>`) to finalize or expire.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "`\"finalize\"` (default, post-challenge payout) or `\"expire\"` (client escrow refund past\nclaim/submit deadline or past `submitted_at + verification_timeout` if never self-verified).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / task_id / description
      Previous value: -"The task identifier (format: `<campaign_id>:<task_uuid>`) of the verified task whose payment should be released."New value: +"Task ID (`<campaign_id>:<task_uuid>`) to finalize or expire."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, non-idempotent and openWorld, so the safety bar is lower; the description nonetheless adds real economic context (pays the agent and recoups any advance vs. refunds client escrow) and the signing/submission flow. It does not state irreversibility or permission requirements explicitly, which keeps it from a 5.

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 compact sentences, front-loaded with the mode split and ending with the required next action. The `[EARN: SOL]` tag and backtick-heavy phrasing are slightly noisy but carry signal and cost little.

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 three-parameter, fully documented, destructive settlement tool with no output schema, the definition covers both modes, their triggering conditions, and the mandatory submission path. What an agent receives after submission is left implicit, which is the only notable gap.

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 all three parameters are already documented, including the mode semantics and the network mismatch warning. The description restates the mode meanings but adds no format, default, or edge-case detail beyond the schema text; baseline 3 applies.

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 ("Settle a task") and enumerates the two settlement modes with their distinct payouts, so an agent can tell this apart from claim/complete/verify siblings. It falls short of 5 because it never explicitly contrasts with the closest siblings (shillbot_complete_task, shillbot_approve_task), leaving the boundary to inference.

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 clear selection criteria between the two modes: finalize for post-challenge agent payout, expire for client escrow refund past the claim/submit deadline or past `submitted_at + verification_timeout` when unverified. It also routes the follow-up step ("Sign locally and submit via shillbot_submit_tx"). No explicit "when not to use" or prerequisite list beyond the deadline condition.

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