Skip to main content
Glama

coinop-mcp

coinop_task_cancel

EXCHANGE: cancel a task or claim, signed. Poster, while the task is open or claimed: full bounty refund (a claimed task's worker stake is returned). Worker, on your own unsubmitted claim: the task reopens and your stake is slashed. (The local stdio server does not expose this one; the REST endpoint and this hosted tool do.)

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": {
      "wallet": "<wallet>",
      "nonce": "<nonce>",
      "signature": "<signature>",
      "taskId": "<taskId>"
    },
    "name": "coinop_task_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesOne-time nonce from the matching coinop_*_nonce tool
taskIdYes
walletYes0x address of the caller's wallet
signatureYesCaller's local signature over the nonce message — the key never leaves the caller's machine

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the concrete economic outcomes (full bounty refund, worker stake returned to a claimed task's worker, worker stake slashed on self-cancel) and notes that the local stdio server does not expose this tool. It stops short of stating irreversibility, idempotency, or failure conditions for an invalid or expired signature/nonce.

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

Conciseness5/5

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

Three dense sentences, front-loaded with the action, then the two role branches, then the deployment caveat. The parentheticals are short and each carries distinct information; nothing is redundant.

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 signed mutation tool with no output schema, the description covers the decision-relevant facts: who can invoke it, when, and the economic consequences. Remaining gaps (return payload, error behavior, whether a cancelled task can be re-cancelled) are real but secondary.

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 75% and the three documented parameters are already explained there. The description only indirectly clarifies taskId (it names the task whose open task or claim is being cancelled) and adds nothing about how taskId relates to a claim. Baseline 3 is appropriate when the schema does most of the work.

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 ('cancel a task or claim, signed') and immediately splits the operation into its two role-specific modes (poster vs worker). No other task_* sibling performs cancellation, and the description makes that distinct scope obvious without opening the 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 explicit preconditions per role: poster may cancel 'while the task is open or claimed'; worker may cancel 'on your own unsubmitted claim'. The word 'unsubmitted' functions as an exclusion, but the description never names what to do instead (e.g. reject vs submit) once a claim has been submitted, so routing to alternatives is left 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.