Skip to main content
Glama

queue_wc_votes

Pre-configure World Congress votes before the next session to skip interactive voting and automatically cast votes based on your preferences.

Instructions

Pre-configure World Congress votes for the upcoming session.

Args:
    votes: JSON array of vote objects, e.g.
        '[{"hash": -513644209, "option": 1, "target": 2, "votes": 5}]'
        hash = resolution type hash (from get_world_congress)
        option = 1 for A, 2 for B
        target = player ID for PlayerType resolutions (from get_world_congress
                 target list, e.g. [target=2] Portugal), or target value for
                 non-player resolutions. The handler resolves to the correct
                 0-based index at runtime.
        votes = max votes to allocate (will use as many as favor allows)

Call this BEFORE end_turn when get_world_congress shows 0 turns until next
session. Registers an event handler that fires during WC processing and
casts your votes with the specified preferences.

If you don't call this, end_turn will pause at the World Congress session
and return control to you for interactive voting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
votesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses that it registers an event handler that fires during WC processing and casts votes. With no annotations, description fully covers behavioral traits including when to call and effect on end_turn.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear purpose, argument explanation, usage instruction, and consequence of not calling. Each sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a single-parameter tool. Covers what, when, how, and alternative behavior. Output schema exists but description adds necessary usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Provides detailed explanation of the votes parameter with example JSON and breakdown of each field (hash, option, target, votes). Schema description coverage is 0%, so description fully compensates.

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

Purpose5/5

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

Clearly states 'Pre-configure World Congress votes for the upcoming session' with specific verb and resource. Distinguishes from sibling tools like get_world_congress and end_turn by focusing on vote configuration.

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

Usage Guidelines5/5

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

Explicitly says 'Call this BEFORE end_turn when get_world_congress shows 0 turns until next session' and explains alternative behavior: 'If you don't call this, end_turn will pause... for interactive voting.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrislin1/civ6-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server