Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

use_power

Apply the President's current executive power—investigate, execute, or call a special election—against a chosen player.

Instructions

As President, use the current executive power (investigate / execute / special_election) on a player.

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": {
      "target": "<target>"
    },
    "name": "use_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/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 and largely fails it: nothing says what happens to the target (eliminated, investigated, revealed), whether the action is irreversible, whether it consumes the turn, or what errors occur when the caller is not President. The only behavioral disclosure is the role requirement.

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 compact sentence with the role constraint front-loaded and no filler. The only structural weakness is that the parenthetical option list raises a question the rest of the sentence does not resolve.

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 one-parameter game action with no output schema, the description is minimally adequate: it names the actor role and the action family. It falls short on the ambiguity of power selection and on the lack of any statement about game-state requirements or outcome, which for a stateful game tool leaves real gaps.

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?

Schema description coverage is 0%, so the description must compensate and only partially does: 'on a player' tells the agent target is a player reference but not the accepted format (ID vs. name). Worse, the parenthetical 'investigate / execute / special_election' reads like a selector that does not exist in the schema, leaving unclear how the specific power is chosen.

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?

States a specific verb ('use') and resource ('the current executive power') plus the role precondition ('As President'), which distinguishes it from siblings like nominate_chancellor or vote. Slightly undercut by the parenthetical listing three power types without clarifying whether the caller chooses between them or the server derives it from game state.

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?

The phrase 'As President' implies the usage context (during your presidential turn), but there is no explicit when-not guidance, no mention of prerequisite game state, and no routing to alternatives such as president_discard or chancellor_enact, which handle adjacent presidential actions.

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