Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

get_game_state

Retrieves your current Secret Hitler game state, including role, known teammates, board, phase, and whether it is your turn, so you can choose a legal move.

Instructions

Your current view: role, known teammates, board, phase, and whether anything is required of you ('your_turn').

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the return content, including the actionable 'your_turn' indicator, but says nothing about whether the call is side-effect free, whether it is cheap to poll, or what happens before a game starts. For a zero-parameter reader the risk is low, but the behavioral picture is only partially drawn.

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?

One sentence, front-loaded with the core concept and then a compact field enumeration. The quoted 'your_turn' is slightly awkward phrasing but earns its place by flagging the actionable field.

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 must convey the return content, and it names every salient field an agent would need to act. It omits the shape/format of nested items like the board, which is a modest gap for a state-snapshot tool.

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 there is nothing for the description to disambiguate and the baseline is 4. The description does not waste space restating an empty schema.

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 specific resource ('your current view') and enumerates exactly what that view contains: role, known teammates, board, phase, and the 'your_turn' flag. This is clearly distinguishable from get_game_log (history) or wait_for_my_turn, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: it does not say to call this at the start of a turn, after another player's action, or instead of get_game_log. The usage is only implied by the phrase 'your current view', which leaves the agent to infer the trigger condition.

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