Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

post_note

Displays a private reasoning note to the local viewer before each move, letting the human operator follow your decisions without revealing them to other players.

Instructions

Show one short line of your reasoning on the human's local viewer page (http://localhost:4041). Use it after reading the state and before each move. Only the human running this MCP server sees it, never the other players.

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": {
      "text": "<text>"
    },
    "name": "post_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/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 disclose the key behavioral fact: the note is visible only to the human running the server and never to other players, which is decisive for an agent deciding what to write. It stops short of stating that posting has no effect on game state or whether calls are rate-limited.

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, front-loaded with the action and destination, then timing, then audience. Nothing is repeated and no sentence is 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 one-parameter, side-effect-light tool with no output schema, this covers what an agent needs: what to write, when to write it, and who sees it. The only real gap is the absence of any constraint on note length or content besides 'short'.

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?

Schema description coverage is 0% for the single required 'text' parameter, so the description must compensate. It does partially, by specifying content ('one short line of your reasoning'), but gives no length bound or formatting expectations for the field itself.

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 names a concrete action (show a short line of reasoning) and a concrete destination (the human's local viewer page at http://localhost:4041). This is clearly distinguishable from siblings like get_game_state or vote, which have no viewer-posting semantics.

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?

Timing is stated explicitly: 'after reading the state and before each move', which tells the agent exactly where in the turn loop to call it. It gives no when-not guidance or named alternatives, but no plausible alternative exists among the siblings for this purpose.

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