Skip to main content
Glama

coinop-mcp

coinop_task_submit

EXCHANGE: submit your claimed task. custom: submission is the deliverable text. arcade_score: submission is the sid of a run you finished after claiming (server verifies and settles instantly). 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>",
      "submission": "<submission>"
    },
    "name": "coinop_task_submit"
  }
}

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
submissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose meaningful behavior: arcade_score submissions are server-verified and settle instantly, while custom submissions are just text. It omits what the caller gets back, whether a submission can be revised or withdrawn, and what happens if verification of a run fails.

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?

Very compact and front-loaded — the primary action leads and the mode-specific semantics follow immediately. The telegraphic phrasing ('Signed: wallet + nonce + signature from coinop_tasks_nonce') saves space at a small cost in readability.

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 five-required-parameter, unannotated mutation with no output schema, the description covers the submission semantics and signing source but not the settlement outcome of the custom path, error behavior, or what the call returns. Adequate to invoke correctly, thin on consequences.

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 60%, and the description compensates on the least self-evident field by defining 'submission' differently per task type (deliverable text vs sid of a finished run). wallet, nonce, and signature are already documented in the schema; taskId is documented in neither place.

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?

The description gives a specific verb and resource (submit a claimed task) and immediately branches by submission kind (custom text vs arcade_score run sid), which no sibling name implies. It stops short of full clarity only because terms like 'custom' and 'arcade_score' are task-type labels that are never defined for an outside caller.

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?

It states the prerequisite (you must have claimed the task) and points at coinop_tasks_nonce as the source of the nonce/signature, which is real routing guidance. It does not cover failure or adjacent paths — e.g. what to do instead if the task is not yet claimed (coinop_task_claim), or how this differs from cancel/reject.

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.