Skip to main content
Glama

coinop-mcp

coinop_claim

Claim your full claimable QTR balance on-chain: pass wallet + nonce + signature from coinop_claim_nonce (signed locally). The claim queues for batch minting.

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>"
    },
    "name": "coinop_claim"
  }
}

Input Schema

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

A4.2/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 behavioral burden and does disclose two non-obvious traits: signing happens locally so the private key never leaves the caller's machine, and the claim is queued for batch minting rather than settled immediately. It omits auth requirements, nonce single-use/idempotency, and failure behavior, which a mutation tool arguably should state.

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 sentences, front-loaded with the action and the amount, then the prerequisites, then the lifecycle outcome. No filler and no restatement of the tool name.

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 3-required-param mutation with no annotations and no output schema, the description covers the input chain and what happens after submission (queued for batch minting). What the caller receives back and how to check claim status are left implicit, though sibling tools like coinop_rewards or coinop_state plausibly cover that.

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 description coverage is 100% and every parameter already documents its own origin and format, so the baseline is 3. The description adds only a modest framing (all three are required together, signature is over the nonce message) that largely restates the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (claim) and resource (full claimable QTR balance) with an explicit scope word, 'full'. It also names the sibling it depends on (coinop_claim_nonce), so an agent can place it in the workflow chain against coinop_task_claim, coinop_insert_coin, and others without opening any schema.

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?

Implies use when the caller has a claimable QTR balance and states the concrete prerequisite chain: obtain nonce + signature from coinop_claim_nonce first. There are no explicit exclusions (e.g., what to do with a zero balance, or whether coinop_claim_nonce must always precede it), 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.