Skip to main content
Glama

New game

new_game

Start a new game. Returns a game_id to pass to step, plus the first board. Games expire after 2 hours without a move.

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": "new_game"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add genuinely useful behavior: it discloses the return payload (game_id plus first board) and a concrete lifecycle limit ("Games expire after 2 hours without a move"). It omits side effects on any existing session, whether state is server-side or client-held, and any auth or rate constraints, leaving meaningful gaps for a state-creating tool.

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: purpose first, output and handoff second, expiry constraint last. Every sentence carries information the agent needs and there is no filler.

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 zero-parameter, no-output-schema tool, the description covers purpose, return value, and expiry — enough to call it correctly. The main residual gap is whether starting a new game invalidates an in-progress one, which matters for sequencing calls alongside step and get_state.

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 the description correctly signals that no configuration is accepted — nothing to mis-specify. It adds the useful note that the identifier needed later comes from the response rather than the request.

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?

The description gives a specific verb and resource ("Start a new game") and immediately names the downstream artifact (game_id for step) plus the first board, which clearly separates it from read-only siblings like get_state and high_scores. It stops short of explicitly contrasting with those siblings, but the purpose is unmistakable.

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?

Usage is implied by the name and the handoff sentence "a game_id to pass to step", which tells the agent what to do next. However, it never states when not to call it — e.g., whether calling it while a game is already in progress replaces or coexists with that game — so the agent must infer lifecycle rules.

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