Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

propose_veto

Propose vetoing the current policy hand when you are Chancellor and five fascist policies are on the board, enabling a legal veto request during Secret Hitler play.

Instructions

As Chancellor with 5 fascist policies on the board, propose vetoing this hand.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It discloses the role and board-state requirement, but not whether this mutates game state, what happens if the president declines, or whether the call errors when preconditions are unmet.

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?

One compact sentence with the precondition and the action packed together and no filler. Slightly dense in phrasing but front-loaded and unambiguous.

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 zero-parameter game action this is close to sufficient, but it omits the resolution path — that the veto requires the president's response via respond_to_veto — which an agent needs to plan the next move in this multi-step game flow.

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 beyond the role/state precondition it already supplies. Schema coverage is 100% trivially.

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 (propose vetoing) and the exact game state that gates it (Chancellor, 5 fascist policies on the board). The 'Chancellor' role qualifier implicitly separates it from respond_to_veto, though it never names the counterpart explicitly.

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 precondition 'As Chancellor with 5 fascist policies on the board' acts as a hard usage gate, which is genuinely useful. But there is no statement of what to do instead when the condition fails, nor any reference to respond_to_veto as the follow-up step.

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