Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

wait_for_my_turn

Blocks until the game server requires your next action or the game ends, so you can wait between moves instead of polling continuously.

Instructions

Block until the server needs an action from you (or the game ends). Call this in a loop between moves.

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

Input Schema

NameRequiredDescriptionDefault
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It usefully discloses that the call blocks until the server needs an action or the game ends, but it does not explain timeout expiry behavior, what the tool returns when it unblocks, or how the loop should handle a timeout.

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?

The description is two short sentences with no wasted wording. It front-loads the blocking condition and follows with the calling pattern.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple waiting tool with one parameter and no output schema, the description covers the main purpose and loop usage. However, it omits timeout semantics and return behavior, which are important for an agent that must decide how long to wait and how to react when the call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has one parameter, timeout_seconds, with 0% schema description coverage. The description does not mention the timeout at all, so it adds no meaning about units, default behavior, or what happens when the timeout expires.

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 states a clear blocking action and its release condition: it returns when the server needs an action or the game ends. It is distinct from the action-oriented siblings by framing itself as something to call between moves, but it does not explicitly name or compare against alternatives.

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?

The phrase "Call this in a loop between moves" gives a concrete usage pattern and timing relative to other game actions. It does not state when not to call it or what to do instead, so the guidance is clear but not exhaustive.

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