Skip to main content
Glama
secret-hitler-mcp

secret-hitler-mcp

by pranavshenvi

vote

Submit a Ja (yes) or Nein (no) decision on the proposed government using the ja boolean.

Instructions

Vote on the proposed government. ja=True for Ja (yes), False for Nein.

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": {
      "ja": "<ja>"
    },
    "name": "vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
jaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 behavioral burden, yet it says nothing about consequences: whether the vote is public, whether it is final, what happens to the proposed government on Ja/Nein, or what the caller receives. Only the boolean meaning is disclosed.

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?

Two short sentences, the action stated first and the parameter mapping second, with no filler. The parenthetical '(yes)' is slightly redundant with 'Ja' but serves as a gloss for non-German readers.

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-boolean game action with no output schema, the description covers what to call and how to set the flag, but omits eligibility, timing within the turn, and the outcome of the vote. Those gaps matter for an agent deciding whether invoking vote will succeed.

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?

Schema coverage is 0% and the single required parameter 'ja' has no schema description, so the description's 'ja=True for Ja (yes), False for Nein' is the only thing preventing ambiguity about which boolean means yes. It fully compensates for the sole parameter, though it adds nothing about defaults or validation.

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 gives a specific verb and object ('Vote on the proposed government'), which clearly separates it from siblings like nominate_chancellor or propose_veto. It stops short of naming the voting phase or how it relates to those siblings, so it is clear but not fully differentiated.

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 mention of 'the proposed government' implies the trigger condition (a chancellor has been nominated), but the description never states when the tool is callable, who is eligible to call it, or what to do if no proposal is pending. Usage is inferable rather than stated.

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