Skip to main content
Glama

coinop-mcp

coinop_insert_coin

Start a play session on a cabinet. USDC path: sign the x402 payment LOCALLY (exactly 0.25 USDC, EIP-3009, Base) and pass it as paymentHeader — call without paymentHeader first to receive the exact 402 terms to sign. QTR path: set payWith 'qtr' and pass wallet + nonce + signature from coinop_qtr_nonce (50 QTR from your claimable balance; the 25 QTR reward lands when the game finishes, net -25). Optional referralCode on your FIRST-EVER coin: when you complete your first game the referrer earns 25 QTR. Returns a sessionToken — pass it to coinop_state / coinop_act / coinop_heartbeat; this hosted server holds NO session state and NO keys.

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": {
      "gameSlug": "<gameSlug>"
    },
    "name": "coinop_insert_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceNoOne-time nonce from the matching coinop_*_nonce tool
walletNo0x address of the caller's wallet
payWithNousdc (default): paymentHeader. qtr: wallet + nonce + signature instead.
gameSlugYesCabinet slug from coinop_games, e.g. snake
signatureNoCaller's local signature over the nonce message — the key never leaves the caller's machine
referralCodeNoOptional: a referrer's QTR-XXXXXXXX code, only meaningful on your first-ever play
paymentHeaderNoBase64 x402 payment payload, signed LOCALLY by the caller's wallet (EIP-3009 transferWithAuthorization for exactly 250000 atomic USDC). Omit it to receive the exact 402 terms to sign. Your private key never leaves your machine — this server cannot sign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does: it discloses that signing happens locally with no server-side keys, that the server holds no session state, the exact amount and standard (0.25 USDC via EIP-3009 on Base), the QTR economics including the 25 QTR reward and net -25 cost, and the sessionToken lifecycle. These are exactly the facts an agent cannot infer from the schema.

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?

Front-loaded with the core action, then cleanly split into labeled 'USDC path' and 'QTR path' segments with the return value last. Dense but almost entirely load-bearing; the economics parenthetical is slightly verbose but relevant to a cost-bearing action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, no-output-schema, no-annotation mutation tool, the description covers prerequisites, both payment branches, side effects (reward payout), the return value (sessionToken), and the follow-up tools. Nothing an agent needs in order to call this correctly is missing.

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 each parameter is already documented in detail, so the baseline is 3. The description reinforces the paymentHeader/nonce/signature relationship and constrains referralCode to first-ever plays, but it largely restates what the schema already says rather than adding new per-parameter meaning.

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?

States a specific verb and resource — 'Start a play session on a cabinet' — and immediately distinguishes the two payment routes (USDC via paymentHeader, QTR via wallet+nonce+signature). An agent knows exactly which resource this creates and how, without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing ('call without paymentHeader first to receive the exact 402 terms to sign'), explicit branch condition for the QTR path, explicit constraint that referralCode is only meaningful on the first-ever coin, and explicit handoff to coinop_state / coinop_act / coinop_heartbeat via sessionToken. It also names coinop_qtr_nonce as the source of the nonce, so the prerequisite chain is unambiguous.

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.