Skip to main content
Glama

coinop-mcp

coinop_task_reject

EXCHANGE: (poster) reject a submitted custom task — full bounty refund to you; the rejection is public record. Signed: wallet + nonce + signature from coinop_tasks_nonce.

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

Input Schema

NameRequiredDescriptionDefault
nonceYesOne-time nonce from the matching coinop_*_nonce tool
reasonNo
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

A3.8/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 well: it discloses the financial consequence (full bounty refunded to the caller), the permanence/visibility of the action ("the rejection is public record"), and the exact auth scheme required. It stops short of saying whether the task is returned to the board, deleted, or what the worker sees.

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?

Two tight sentences with the action, actor, consequence, and signing requirement front-loaded; the "EXCHANGE:" tag orients the agent to the category before the verb. No 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 5-parameter mutation with no output schema and no annotations, the definition covers actor, effect, side effects, and auth flow. The remaining gap is post-state clarity (what happens to the task and worker on rejection) and the role of the reason parameter.

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 60%, so the schema documents wallet, nonce, and signature while taskId and reason are bare. The description adds real value by tying nonce provenance to coinop_tasks_nonce and framing the three fields as a signing triple, but it says nothing about the semantics of reason or which taskId is eligible.

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?

Names a specific verb and resource ("reject a submitted custom task") and scopes it to the poster role, which distinguishes it from accept/cancel/claim siblings by actor rather than by name. It never explicitly names an alternative, but the action is unambiguous.

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?

"(poster)" and "submitted" imply the actor and the lifecycle point at which the tool applies, but there is no explicit when-not guidance (e.g. use coinop_task_accept instead if the work is satisfactory) and no statement of preconditions such as deadline windows.

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.