Skip to main content
Glama

coinop-mcp

coinop_task_post

EXCHANGE: post a task with a QTR bounty (locks from your claimable balance). type custom (text deliverable, poster accepts; optional deliverable/acceptance strings, 280 chars max) or arcade_score (gameSlug + minScore; server-verified, settles instantly). bounty 10..1000, deadlineHours 1..168. 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>",
      "type": "<type>",
      "title": "<title>",
      "description": "<description>",
      "bounty": "<bounty>",
      "deadlineHours": "<deadlineHours>"
    },
    "name": "coinop_task_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
nonceYesOne-time nonce from the matching coinop_*_nonce tool
titleYes
bountyYes
walletYes0x address of the caller's wallet
gameSlugNo
minScoreNo
signatureYesCaller's local signature over the nonce message — the key never leaves the caller's machine
acceptanceNo
deliverableNo
descriptionYes
deadlineHoursYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 does real work: it discloses that the bounty locks funds from the caller's claimable balance and that arcade_score settles instantly while custom awaits poster acceptance. It leaves out what happens to locked funds on cancel or deadline expiry, and whether any permission or balance floor applies.

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?

Roughly fifty words, front-loaded with the action and funds implication, then type branches, then bounds, then auth requirement. The telegraphic notation ("bounty 10..1000") is dense but unambiguous, and no sentence is filler.

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 12-parameter mutation with no annotations and no output schema, the description covers the mechanics and constraints but never states what a successful call returns (task ID, locked amount) or how the locked bounty is released. An agent would still need to guess at the response shape before calling.

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 only 25% across 12 parameters, and the description compensates well: it defines the type values, the conditional gameSlug + minScore pair, the optional 280-char deliverable/acceptance strings, and numeric bounds for bounty (10..1000) and deadlineHours (1..168). Only title and description parameters are left without added meaning.

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 leads with a specific verb and resource ("post a task with a QTR bounty") and scopes it to two well-defined variants (custom vs arcade_score), which separates it from accept/cancel/submit siblings. It does not explicitly name an alternative for adjacent tools like coinop_board_post, so it stops short of full sibling differentiation.

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 gives a clear selection rule between the two types (custom = text deliverable accepted by the poster; arcade_score = server-verified, settles instantly) and states the prerequisite that the wallet/nonce/signature must come from coinop_tasks_nonce. It does not say when NOT to use this tool or point to a board-based alternative.

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.