Skip to main content
Glama

game_find_evm_match

Destructive

[STATE] Join the same-chain EVM Coordination Game queue (EVM vs EVM — no session key or float pool; both players stake into one CoordinationGame contract, resolved from the chain registry). Live on Mainnet (Base, Ethereum — prefer Base over Ethereum L1 for ~$5 stakes) and Testnet (Base Sepolia). Requires a registered EVM (0x) wallet. Returns 'waiting' (poll game_evm_match_status) or 'matched' with two unsigned calls {create_call, join_call} — the waiting player sends createGame, the joiner joinGame.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_find_evm_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
tournament_idNoTournament ID to join. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description goes further: it explains that both players staking funds into a single CoordinationGame contract resolved from the chain registry, states the wallet prerequisite, names the supported networks, and describes both return states ('waiting' vs 'matched' with two unsigned calls) and which caller sends createGame vs joinGame. This is unusually rich behavioral context beyond the annotation flags.

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?

The definition is dense but front-loaded with the action and the EWM-vs-EWM scope, then networks, then prerequisite, then return contract. Parenthetical clauses pack in useful detail without much waste; a slightly tighter split into sentences would read better, but nothing is redundant.

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?

With no output schema, the description carries the return contract itself and does so well (two named states, unsigned call shape, role assignment). Prerequisites and network support are covered. The only gap is stake amount/denomination behavior and any queue timing expectations, which are minor for a queue-join tool.

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?

There is a single optional parameter, tournament_id, with 100% schema description coverage ('Tournament ID to join. Defaults to 1'). The tool description adds nothing about it, but the schema already carries the meaning, so the baseline 3 applies.

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 — 'Join the same-chain EWM Coordination Game queue (EVM vs EWM)' — and immediately narrows scope against alternatives by stating 'no session key or float pool; both players staking into one CoordinationGame contract'. An agent can distinguish this from the cross-chain variants in the sibling list 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?

It statesA clear context:<br>conditions: requires a registered EWM (0x) wallet, live on Mainnet (Base, Ethereum) and Testnet (Base Sepolia), and it recommends Base over Ethereum L1 for ~$5 staking. It also points to game_evm_match_status for the 'waiting' follow-up. It does not explicitly say when to choose this over game_find_match or xchain_find_match, but the same-chain framing implies the distinction.

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.

Resources