Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

finish_turn

Acknowledge a President policy peek or end your term when the game prompts you to continue.

Instructions

As President, acknowledge a policy peek or end your term when the game asks you to continue.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a state transition that yields control but does not say whether the call is required, whether it mutates game state, what happens if called out of turn, or what the caller receives.

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 sentence with the condition ('when the game asks you to continue') and the actions packed together, no filler. It could be slightly clearer by separating the two branches, but nothing is wasted.

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 parameterless, output-less turn-advance tool, the description covers the trigger and the two possible situations, which is roughly adequate. It still leaves gaps on failure behavior and confirmation of what the call accomplishes, which matter for an agent driving a turn-based game loop.

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 clarify beyond the schema. Baseline 4 applies.

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

Purpose3/5

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

The description names a role ('As President') and two concrete outcomes ('acknowledge a policy peek' or 'end your term'), which is more specific than the name alone. However, 'finish_turn' is not clearly differentiated from siblings like president_discard or use_power, and the phrase 'acknowledge a policy peek' is opaque without game context.

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 trigger 'when the game asks you to continue' gives an implied when-to-use condition, which is useful. There is no explicit statement of alternatives (e.g., what to call instead if it's not your turn) or when this should not be used.

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