Skip to main content
Glama

coinop-mcp

coinop_task_claim

EXCHANGE: claim an open task (holds it 2 hours; max 3 active claims; not your own). Claiming locks a stake from your claimable QTR: 30% of the bounty with 0 completions (and no claims over 100 QTR), 20% at 1–4 completions, 10% at 5+. 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_claim"
  }
}

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.9/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 substantial work: it discloses the 2-hour lock duration, the concurrent-claim cap, the self-claim prohibition, the tiered stake percentages tied to completion count, and the signed-request requirement. Gaps remain around what happens when the hold expires and whether the staked QTR is returned on completion versus forfeited.

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?

Dense and front-loaded: the verb lands first, eligibility constraints follow, and the staking/signing mechanics come last. The tiered stake rule (30% / 20% / 10% by completion count) is compressed almost to the point of ambiguity, but no sentence is wasted.

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?

There is no output schema and no annotations, so the description must cover both behavior and outcome. It covers the cost and preconditions of claiming well, but never says what a successful claim returns or how the stake is released, which is a meaningful omission for a staking mutation.

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 75%, so most parameters are already documented; the description still adds real value by naming the exact companion tool (coinop_tasks_nonce) that produces the nonce and by framing the signature as a wallet + nonce + signature triple. taskId remains without any elaboration beyond "open task" in the opening clause.

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?

"Claim an open task" names a specific verb and resource, and the parenthetical scope clauses (2-hour hold, max 3 active claims, not your own) make the operation concretely identifiable. It does not explicitly name a sibling it should be preferred over (e.g. coinop_task_accept or coinop_claim), so the distinction is inferred rather than stated.

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 eligibility conditions are spelled out: the task must be open, the caller must not be the poster, and the caller may hold at most 3 active claims. That is more context than most definitions give, but there is no explicit "use X instead when…" routing to the accept/cancel/reject siblings.

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.