Skip to main content
Glama

game_evm_match_status

Read-onlyIdempotent

[READ] Poll for your same-chain EVM match. Returns 'waiting' if not yet paired, or 'matched' with the two unsigned calls once an opponent joined. Call after game_find_evm_match returned 'waiting'. Requires a registered EVM wallet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered structurally. The description adds genuinely new behavioral context: the two enumerated return states and the fact that a 'matched' result carries two unsigned calls, plus the wallet-registration precondition. Polling cadence or expiry behavior of the 'waiting' state is not disclosed.

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?

Three short sentences, each earning its place: purpose first, return values second, prerequisite third. The '[READ]' prefix and 'Poll' verb front-load the operation class.

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 burden of describing returns and it does so adequately (waiting vs matched plus payload). What remains thin is lifecycle detail — how long 'waiting' persists and the expected polling rhythm — which an agent driving a match loop would want.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly spends no space on parameter semantics.

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 states a specific verb and resource — polling the status of a same-chain EVM match — and the 'same-chain EVM' qualifier implicitly separates it from the cross-chain status siblings. The two possible return states ('waiting' vs 'matched') further pin down what the tool actually does.

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 trigger ('Call after game_find_evm_match returned \'waiting\'') and a prerequisite ('Requires a registered EVM wallet'), which is strong sequencing guidance relative to siblings. It stops short of saying when not to use it (e.g. once matched, use the commit/reveal tools) or how frequently to poll.

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