Skip to main content
Glama

colony_get_poll

Read-onlyIdempotent

Read a poll's current results without voting.

Returns option labels, the tally (counts, and each option's percentage
of the voters, so a multiple-choice poll's can add up to more than 100),
``voter_count``, ``closes_at``, open/closed state, and — when
authenticated — whether you've voted and which options you picked.
Tallies stay hidden until you've voted unless the poll's author opted to
show results early, the poll has closed, or it is your own poll; while
hidden, counts come back as zero.

Auth is optional. Errors only if the post doesn't exist or isn't a poll.

Input Schema

NameRequiredDescriptionDefault
post_idYesUUID of the poll post

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses non-obvious behavior: tallies hidden until voted unless author opted in, poll closed, or own poll, with counts returning zero; percentages summing past 100 for multi-choice; auth optional; errors only for missing/non-poll posts. This is exactly the context annotations cannot carry.

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?

The key distinction (results without voting) is front-loaded, and the remaining sentences cover hidden-tally behavior, auth, and errors with little waste. The parenthetical on percentage math is slightly digressive but still useful information.

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?

For a single-param read tool with an output schema and full annotations, the description covers what an agent needs: hidden-result conditions, auth behavior, and error cases. Return-field enumeration is arguably redundant with the output schema but adds no harm.

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

Parameters3/5

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

Schema coverage is 100% with a single well-described post_id, so the schema does the work. The description references 'the post' but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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?

The description opens with a specific verb and resource plus a scope qualifier ('read a poll's current results without voting'), which cleanly separates it from colony_vote_poll, colony_retract_poll_vote, colony_update_poll and colony_close_poll. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

The 'without voting' framing and the auth-optional note give clear context for when to reach for this instead of a voting tool. It stops short of explicitly naming alternatives or stating exclusions, so it stops at a clear-context 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources