Skip to main content
Glama

get_poll_consensus

Analyze vote distribution and calculate optimal meeting slot with percentage agreement, voter breakdown, and AI scheduling recommendations

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": {
      "poll_id": "<poll_id>"
    },
    "name": "get_poll_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
poll_idYesPoll ID or vanity slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / poll_id / description
      Previous value: -"Poll ID or vanity slug [Required: non-empty valid value must be supplied]."New value: +"Poll ID or vanity slug"
  2. Changed1 schema field changed
    • changedInput schema / properties / poll_id / description
      Previous value: -"Poll ID or vanity slug"New value: +"Poll ID or vanity slug [Required: non-empty valid value must be supplied]."
  3. First observed

TDQS

B3.2/5.0
Behavior3/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. It discloses the computed outputs (percentage agreement, voter breakdown, AI recommendations), which is useful, but it does not explicitly confirm this is a read-only operation, describe error conditions, or state whether analysis requires any poll state.

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 description is a single front-loaded sentence that leads with the core action and then enumerates key outputs. It is efficient and contains no wasted preamble, though 'AI scheduling recommendations' is somewhat promotional.

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?

There is no output schema, so the description should explain the return shape more fully. It lists three output components, which is helpful, but leaves out structural details (e.g., format of the voter breakdown or the recommendation) and any preconditions for successful analysis.

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 description coverage is 100%, and the schema already documents the sole parameter 'poll_id' as a poll ID or vanity slug. The description adds no further parameter semantics, so the baseline of 3 applies.

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 uses a specific verb+resource combination ('Analyze vote distribution', 'calculate optimal meeting slot') that clearly identifies what the tool does. It is distinguishable from the sibling tools (create_meeting_poll, submit_participant_vote) by being an analysis/read operation, though it never explicitly names those alternatives.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, nor any stated prerequisites such as whether votes must already be submitted or whether the poll must be closed. Usage is only weakly implied by the word 'Analyze'.

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