Skip to main content
Glama

coinop-mcp

coinop_join_match

VERSUS: join an open duel by matchId. Sign the 0.25 USDC stake LOCALLY and pass it as paymentHeader — call without paymentHeader first to receive the exact 402 terms. Starts your run (snake: same seed as the creator) and returns your sessionToken. Finish within 10 minutes or forfeit.

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": {
      "matchId": "<matchId>"
    },
    "name": "coinop_join_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchIdYes
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.7/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 it: it discloses the 0.25 USDC stake requirement, that signing must happen locally and the private key never reaches the server, that the call starts your run inheriting the creator's seed, that a sessionToken is returned, and that there is a 10-minute forfeit window.

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?

Five short clauses, front-loaded with the purpose, then the payment procedure, then the outcome and the deadline. No filler and no repetition of the schema.

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?

No annotations and no output schema exist, so the description must explain economics, auth, return value, and time limits — and it covers all four (stake amount, local signing, sessionToken, 10-minute forfeit). An agent has everything needed to call this correctly.

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?

The schema describes paymentHeader thoroughly but leaves matchId bare; the description compensates by saying the matchId must identify an open duel and that the signed stake payload goes in paymentHeader, including the omit-to-get-terms behavior. The only remaining gap is what formats or states a valid matchId can take.

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?

"join an open duel by matchId" gives a specific verb, resource, and keying parameter, and the "VERSUS" prefix plus "open duel" separates it from coinop_create_match or listing tools an agent might otherwise pick.

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 spells out the two-phase invocation pattern: call first without paymentHeader to receive the exact 402 terms, then sign and retry with the header. It does not name the alternative tool for opening a new duel instead of joining one, so there is no explicit exclusion, but the decision context is clear.

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.