Skip to main content
Glama
loomiomcp
by soil-dev

list_polls

Read-onlyIdempotent

Retrieve a group's polls newest first, filter by active/closed/all status, and control detail length or HTML stripping to review options and visible scores.

Instructions

One group's polls, newest first: 1 call. status defaults to 'active' ('closed', 'all'); description_max_chars caps details; strip_html (default true). Slim rows with poll_options[] and scores_by_option when visible (trust results_visible). For member activity use get_participation_report, not this plus list_memberships.

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": {
      "group_id": "<group_id>"
    },
    "name": "list_polls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-200. Default 50.
offsetNoPage offset. Default 0.
statusNo'active' (default) = open, 'closed', 'all'.
group_idYes
strip_htmlNoPlain text instead of HTML; default true.
description_max_charsNoChars per `details`; default 1500, 0 omits it, -1 = full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.0.13
    • addedInput schema / properties / description_max_chars
      Added value: +{
      +  "description": "Chars per `details`; default 1500, 0 omits it, -1 = full.",
      +  "maximum": 9007199254740991,
      +  "minimum": -1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / group_id / description
      Removed value: -"ID of the Loomio group whose polls to list (required)."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size. Loomio defaults to 50."New value: +"Page size, 1-200. Default 50."
    • changedInput schema / properties / offset / description
      Previous value: -"Page offset. Defaults to 0."New value: +"Page offset. Default 0."
    • changedInput schema / properties / status / description
      Previous value: -"Filter polls by status. Loomio defaults to 'active'."New value: +"'active' (default) = open, 'closed', 'all'."
    • addedInput schema / properties / strip_html
      Added value: +{
      +  "description": "Plain text instead of HTML; default true.",
      +  "type": "boolean"
      +}
  2. First observedv0.0.6

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds real behavioral context beyond them: rows are 'slim' and include poll_options[] and scores_by_option 'when visible', plus the instruction to trust results_visible. It does not cover pagination behavior or failure modes, keeping it short of a 5.

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?

Front-loads the resource and ordering, then packs parameter behavior and the alternative-routing note into two tight sentences with no filler. The telegraphic phrasing (semicolon chains, backtick fragments) is efficient but slightly terse for readability.

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?

There is no output schema, so the description usefully sketches the return shape (slim rows, poll_options[], scores_by_option, results_visible) and the default filtering behavior. Limit/offset semantics are left entirely to the schema, which is acceptable but a minor gap for a paginated list tool.

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?

With 83% schema coverage the baseline is 3, but the description adds meaning on top: it restates that status defaults to 'active' with the ('closed', 'all') alternatives, that description_max_chars caps details, and that strip_html defaults true. group_id remains undocumented in both places, so it does not fully compensate.

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?

States the resource ('One group's polls'), the ordering ('newest first'), and the call cost ('1 call'), which lets an agent distinguish it from get_poll and create_poll immediately. The scope is unambiguous.

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 routes the agent away from a wrong path: 'For member activity use get_participation_report, not this plus list_memberships.' That is a concrete when-to-use-other guidance with a named alternative and an anti-pattern, which is the strongest form of this dimension.

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