Skip to main content
Glama

Check the result

game_result
Read-only

Checks a finished game and returns the verified score, share text with emoji, and a challenge link a friend can open to play the same board. Records an anonymous play count for the site's stats; nothing about the user.

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": {
      "game": "<game>",
      "number": "<number>",
      "progress": "<progress>"
    },
    "name": "game_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesWhich game, by id from list_games (for example "thunk").
hintsNoHow many hints the player took.
numberYesBoard number (No. 1 was the game's first day).
secondsNoTime spent in seconds, if known.
progressYesEverything the player has done on this board from the start, in the game's own format (list_games describes each). Empty for nothing yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The description states that the tool 'Records an anonymous play count for the site's stats,' which is a persistent write side effect, while the annotations declare readOnlyHint=true. This is a direct contradiction of the structured safety profile. The disclosure is otherwise useful, but the conflict undermines trust in the annotations.

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?

Two tightly written sentences with the outcome first and the side-effect disclosure second. There is no filler, though the side-effect sentence creates the annotation conflict rather than clarifying safe behavior.

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 valuably explains the return payload: verified score, share text, and challenge link. Parameters are fully covered by the schema. The main gap is that the readOnly contradiction leaves the agent uncertain whether invoking the tool has write consequences.

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?

Schema description coverage is 100%, so all five parameters are already documented in the input schema, including game ids, board numbers, progress format, hints, and seconds. The description adds no parameter-level meaning beyond the schema, which is the baseline expectation at full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Checks a finished game') and enumerates the returned artifacts (verified score, share text with emoji, challenge link), which makes the tool's role clear against play-oriented siblings. It does not explicitly name game_move or play_game, so sibling differentiation is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'finished game' implies the tool is for post-game result reporting rather than mid-game actions, but there is no explicit when-to-use guidance or named alternative for ongoing play. The agent must infer the boundary from context.

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