Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

start_game

Initiates a Secret Hitler Online game from the lobby once 5–10 players with icons have joined.

Instructions

Start the game (any player in the lobby can; needs 5-10 players, all with icons).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavior burden; it does disclose the permission model and lobby-state prerequisites, which is meaningful. However, it says nothing about what happens after the call succeeds (state transition, turn order, deal behavior) or what failure looks like, leaving the agent to infer the effects of this state-changing action.

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?

A single front-loaded sentence with the core action first and the constraints packed into a parenthetical. There is no redundant or filler wording, and the essential gating information appears before the reader can stop reading.

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, zero-annotation, no-output-schema state transition, the description covers the two things an agent most needs: who may invoke it and what lobby conditions must hold. What is missing is the post-call effect and error signal, which matters slightly more here because siblings like get_game_state could otherwise confirm readiness.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is a 4. The parenthetical constraints describe server-side preconditions rather than call arguments, so they do not substitute for parameter documentation.

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 ('Start the game'), which is unambiguous and clearly distinct from sibling actions like join_lobby or finish_turn. It adds scope detail (who may trigger it, minimum lobby composition) rather than just restating the name.

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?

Explicitly states the authorization rule ('any player in the lobby can') and the gating preconditions ('needs 5-10 players, all with icons'), which tells the agent exactly when the call is valid. It does not name an alternative action for when preconditions fail, but the exclusion is effectively implied by the stated requirements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.