Skip to main content
Glama

WhichDateWorks

Get poll results

get_poll_results
Read-onlyIdempotent

See how people voted on a WhichDateWorks poll and which option is winning. Pass the poll's id or its invite link. Shows what the public poll page shows: if the organizer hid scores or participant names, they stay hidden.

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

Input Schema

NameRequiredDescriptionDefault
pollIdNoThe poll's id from create_poll.
inviteUrlNoThe poll's invite link, if you don't have its id.

Output Schema

NameRequiredDescriptionDefault
titleYes
pollIdYes
statusYes
optionsYes
timeZoneYes
inviteUrlYes
scoresHiddenYesThe organizer hid the scores: vote counts are not available, only the options.
participantCountYes
participantsHiddenYesThe organizer hid who voted: counts only, no names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results mirror the public poll page, so organizer-hidden scores or participant names remain hidden, warning the agent that results may be incomplete. It stops short of covering failure cases such as an invalid id or a closed poll.

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?

Three short sentences, front-loaded with what the agent gets back, then how to call it, then the visibility caveat. Nothing is wasted and there is no filler or repetition.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the privacy caveat covers the main surprise an agent could hit. The only remaining gap is the zero-required-parameter edge case, where neither id nor invite link is supplied, and what error surface that produces.

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%, so both parameters are already documented, including the inviteUrl fallback. The description restates the either/or choice without adding format details, so it meets but does not exceed the baseline.

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?

A specific verb and resource: it reads votes on a WhichDateWorks poll and reports the leading option. That is clearly distinct from the only sibling, create_poll, though the description never names it explicitly, so differentiation is inferred rather than stated.

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?

Usage is only implied by the read-the-results framing. The sentence about passing an id or invite link is parameter guidance, not when-to-use guidance, and there is no statement about when not to call this or what to do instead.

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