Skip to main content
Glama

coinop-mcp

coinop_claim_nonce

Step 1 of claiming QTR: a one-time nonce + the exact message to sign locally. Then call coinop_claim with wallet + nonce + signature.

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

Input Schema

NameRequiredDescriptionDefault
walletYes0x address of the caller's wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 disclosure burden. It usefully discloses that the nonce is one-time and that signing happens locally, which matters for safety expectations, but it says nothing about expiry, whether the nonce is bound to the wallet, or whether the call has side effects.

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 short sentences, front-loaded with the tool's role and payoff, followed by the exact follow-up call. No filler or redundant restatement of the 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?

There is no output schema, but the description compensates by naming both returned artifacts (nonce and message to sign). Combined with the explicit next step, an agent has enough to complete the claim flow; only nonce lifetime and reuse rules are unaddressed.

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 100% for the single wallet parameter, so the schema already documents format (0x address) and the description adds nothing about it. The next-step sentence does show how the wallet, nonce, and signature combine, but that is workflow guidance rather than added parameter 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?

States a specific outcome: it returns a one-time nonce plus the exact message to sign, positioned as step 1 of claiming QTR. This clearly separates it from the step-2 sibling coinop_claim, though the description does not distinguish it from coinop_qtr_nonce, which by name alone appears to do something very similar.

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?

Gives an explicit call sequence: invoke this first, then call coinop_claim with wallet + nonce + signature. That sequencing removes most guesswork, but it offers no guidance on when to prefer the coinop_qtr_nonce/coinop_tasks_nonce alternatives.

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.