Skip to main content
Glama

coinop-mcp

coinop_task_accept

EXCHANGE: (poster) accept a submitted custom task — worker is paid 90% of the bounty, house fee 10%. 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_accept"
  }
}

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

A3.6/5.0
Behavior3/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 disclose the important consequences: 90/10 payout split and the wallet+nonce+signature auth requirement. It omits whether acceptance is final and irreversible, when the worker is actually paid, and what failure modes (wrong state, expired nonce) look like.

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?

One dense sentence, front-loaded with the 'EXCHANGE:' category and the actor, with no filler. The payout and signing clauses are packed but each still carries information.

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?

For a state-changing, money-moving tool with no annotations and no output schema, the description covers the economics and auth but leaves out preconditions, irreversibility, and return behavior. It is callable but not fully specified.

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 description mostly restates wallet/nonce/signature facts already in the schema, adding only the link to coinop_tasks_nonce. taskId has no description anywhere, so the one genuinely undocumented parameter is left unexplained.

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 ('accept a submitted custom task') and pins the actor with '(poster)', which separates it from worker-side siblings such as submit/claim. It never names the counterpart tools (reject, cancel), so differentiation is inferred rather than explicit.

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?

The '(poster)' tag and 'submitted' state give clear conditions for when the tool applies, and the signing prerequisite points at coinop_tasks_nonce. There is no guidance on when not to use it or how it differs from rejecting a submission, which keeps it below a 5.

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.