Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

get_game_log

Retrieves the full game history—elections, votes, enacted policies, executions—plus your private card and investigation records for review.

Instructions

History of elections, votes, enacted policies and executions, plus your private info (cards you saw, investigations).

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_log"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 burden. It usefully discloses that results are scoped per-player ("your private info") and mixes public history with hidden data, but it says nothing about ordering, time window, completeness, or that the call is a side-effect-free read.

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?

A single dense sentence with no filler, front-loaded on the main content category. Slight compression cost: terms like "executions" are domain shorthand, and the public/private split is buried in a trailing clause rather than structured.

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?

No output schema, no parameters, and no annotations, so the description must convey what comes back — and it does list the content categories. It stops short of describing format, ordering, or whether the log spans the whole game or the current round, which an agent would want to know before relying on it.

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; baseline 4 applies. The description's categorization of returned content is a reasonable substitute for parameter guidance.

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 names a specific resource and enumerates its contents: elections, votes, enacted policies, executions, plus private per-player info such as seen cards and investigations. That is concrete enough to distinguish it in spirit from get_game_state (current state) and the action tools, though it never explicitly contrasts itself with a sibling.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it needs past events or its own hidden information, but the description states no trigger condition, no exclusions, and no pointer to get_game_state as the alternative for current state.

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