Skip to main content
Glama

Play a puzzle

play_game
Read-only

Open a daily puzzle: today's board for a game, or an older one by number. Shows an interactive board the user plays in the chat, plus a text version of the board and the rules.

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>"
    },
    "name": "play_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe user's local date (YYYY-MM-DD), so "today" matches their day. Optional.
gameYesWhich game, by id from list_games (for example "thunk").
numberNoBoard number (No. 1 was the game's first day). Leave out for today's board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real added value is disclosing the response shape — an interactive chat board plus a text board and rules — which is useful since there is no output schema. It does not say whether re-opening an already-played board is allowed or what happens on an invalid number.

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?

Two short sentences with zero filler; the primary action comes first and the return-shape detail follows. Nothing is repeated or padded.

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?

For a three-parameter tool with no output schema, the description covers purpose, source of the game id, and the content the agent will receive. Edge cases such as out-of-range board numbers or replaying a completed board are left to the schema or unspecified.

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 coverage is 100%, so all three parameters are already documented in detail, including the date pattern and the 'No. 1 was the game's first day' note. The description's 'today's board... or an older one by number' restates the date/number choice rather than adding new semantics, so the baseline of 3 applies.

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 ('Open a daily puzzle... today's board for a game, or an older one by number') and adds that it renders an interactive board with rules. The scope is clearly a board-opening action, distinct from move/hint/result tools, though it never explicitly contrasts itself with those siblings.

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?

Implies the trigger (user wants to play a puzzle) and routes parameter discovery to a sibling by specifying the game id comes 'from list_games'. It gives the today-vs-older selection rule but no explicit when-not-to-use guidance.

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