Skip to main content
Glama

game_find_match

Destructive

[SPEND: the configured stake] Build an unsigned deposit_stake tx to join the matchmaking queue; sign locally and submit via game_submit_tx. The ante (GlobalConfig.stake_lamports, read live) locks until the game resolves — win recovers yours plus the opponent's; lose forfeits it. Negative-sum on average after the treasury cut. Requires register_wallet first.

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

Input Schema

NameRequiredDescriptionDefault
networkNoSolana network. `"mainnet"` (default) or `"devnet"`. Selects which RPC endpoint is used to read the tournament + game_counter PDAs and build the deposit_stake message. Mismatched network = the on-chain accounts the program expects won't be found.
tournament_idNoTournament ID to join. Defaults to the tournament currently accepting play (chain-registry::active_tournament_id); omit unless you know what you're doing.

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?

Annotations already declare destructive=true, openWorld=true and non-idempotent, and the description adds real substance beyond them: the stake is read live from GlobalConfig.stake_lamports, funds lock until the game resolves, and the win/lose payout asymmetry plus 'negative-sum on average after the treasury cut' are disclosed. It also makes clear the tool only constructs an unsigned transaction and never signs or sends it.

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 sentences, each doing distinct work: purpose, follow-up path, lock/payout mechanics, expected-value warning, prerequisite. The leading '[SPEND: ...]' tag front-loads the cost signal, which is exactly what an agent needs before committing.

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 output schema exists, yet the description says what is produced (an unsigned deposit_stake transaction) and what the caller must do with it. Combined with the prerequisite, stake source, and payout rules, nothing an agent needs in order to invoke 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?

With 100% schema description coverage, the schema already documents both network and tournament_id, including the warning to omit tournament_id. The description adds only indirect context ('the configured stake', the live GlobalConfig read) and does not itself clarify either parameter, so 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?

States a specific verb and resource ('Build an unsigned deposit_stake tx to join the matchmaking queue') and immediately distinguishes the follow-up step by naming game_submit_tx for signing/submission. An agent can tell this apart from the submit and status siblings without opening another 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?

Gives explicit sequencing (build here, sign locally, submit via game_submit_tx) and a hard prerequisite ('Requires register_wallet first'). It stops short of stating when NOT to use this tool, e.g. routing cross-chain or EVM variants to xchain_find_match or game_find_evm_match, so the alternative-map is incomplete.

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