Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

join_lobby

Join an existing Secret Hitler Online lobby as a player or reconnect to a game after disconnecting by providing the lobby code or invite link and player name.

Instructions

Join an existing lobby as a player (or rejoin a game you were disconnected from). The host creates the lobby in the browser and shares the code. lobby_code may also be a full invite link (e.g. https://secret-hitler.online/?lobby=ABCD); server_url may be the public website, which is mapped to its game backend.

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": {
      "lobby_code": "<lobby_code>",
      "player_name": "<player_name>"
    },
    "name": "join_lobby"
  }
}

Input Schema

NameRequiredDescriptionDefault
lobby_codeYes
server_urlNohttp://localhost:4040
player_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 whole behavioral burden. It usefully discloses the reconnection use case and the invite-link/server_url mapping, but says nothing about failure modes such as an invalid or full lobby, whether joining as an existing name resumes a seat, or what the call returns.

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?

Three short sentences with the primary action front-loaded, followed by the precondition and the parameter quirks. Nothing is padded, though the invite-link and server_url details could be tightened into one sentence.

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 simple three-parameter tool with no output schema and no annotations, the description covers purpose, prerequisite, reconnection behavior, and the non-obvious parameter formats. Only error and result behavior is left unaddressed.

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?

Schema description coverage is 0%, so the description must compensate, and it does for two of three parameters: lobby_code accepts a full invite link, and server_url may be a public website mapped to its game backend. player_name is left unexplained, but its meaning is self-evident from the name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Join an existing lobby as a player'. It also names a second mode ('rejoin a game you were disconnected from'), which distinguishes it from siblings like start_game or wait_for_my_turn.

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?

It gives clear preconditions: the host creates the lobby in the browser and shares the code, so an agent knows a code must exist before calling. It does not explicitly name start_game as the alternative for creating a lobby, which keeps it below a 5.

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