Skip to main content
Glama

coinop-mcp

coinop_create_match

VERSUS: create a head-to-head duel on a cabinet. Sign the 0.25 USDC stake LOCALLY (x402, payTo = the match escrow) and pass it as paymentHeader — call without paymentHeader first to receive the exact 402 terms. Starts YOUR run immediately and returns your sessionToken; a rival must join within 10 minutes or you are refunded in full. Winner gets their stake back + 25 QTR; loser's stake goes to the treasury; draw refunds both and pays both 25 QTR.

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_create_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameSlugYes
referralCodeNoOptional: a referrer's code, only meaningful on your first-ever coin
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.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: local signing with the private key never leaving the machine, the 402 challenge flow, the 10-minute join deadline and full refund, the winner/loser/draw payout rules including the 25 QTR bonus and treasury destination. These are non-obvious economic and timing consequences an agent could not 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 action, then the payment mechanics, then the outcome economics — a logical order with no filler sentences. It is dense and slightly long, but nearly every clause carries decision-relevant information about money or timing.

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 money-moving mutation with no annotations and no output schema, it covers payment prerequisites, deadline, refunds, and payout splits. It stops short of describing the full return payload beyond sessionToken or any auth/rate-limit constraints, which leaves a modest gap for a financial tool.

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 67% and the description adds meaning beyond it by mapping 0.25 USDC to the escrow payTo and clarifying the two-phase paymentHeader protocol. However, gameSlug has no schema description and the description never explains that it names the cabinet/game, leaving the required parameter's semantics underspecified.

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?

The description opens with a specific verb and resource — 'create a head-to-head duel on a cabinet' — and immediately distinguishes this from joining by stating 'a rival must join within 10 minutes' and 'Starts YOUR run immediately'. An agent can tell this apart from coinop_join_match without inspecting either 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?

It gives an explicit procedural rule: 'call without paymentHeader first to receive the exact 402 terms', which is exactly the sequencing an agent needs. It does not explicitly say when to prefer creating over joining an existing match via coinop_join_match or browsing coinop_list_matches, so routing guidance is clear but not exhaustive.

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.