Skip to main content
Glama
soil-dev

loomiomcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_polls

Read-onlyIdempotent

Retrieve a group's polls newest first, filtering by active, closed, or all. Supports pagination and plain-text details to review poll questions and options.

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 stance_counts when visible (trust results_visible). For member activity use get_participation_report, not this plus list_memberships.

Input Schema

TableJSON 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.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds real behavioral detail beyond them: newest-first ordering, slim rows, conditional presence of poll_options[] and stance_counts gated by results_visible, and the effect of strip_html on details. It still doesn't state pagination behavior or total counts, so not 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?

Dense and front-loaded, with the scope/ordering statement first and the routing caveat last. The telegraphic fragment style ('1 call', semicolon-joined clauses) is efficient but slightly cryptic and costs a point on readability.

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?

With no output schema, the description compensates by describing the row shape (poll_options[], stance_counts, results_visible) and the `details` field. Combined with schema-documented paging and defaults, an agent has everything needed to call it correctly.

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?

Schema coverage is 83%, so the baseline is 3. The description adds semantic links the schema doesn't make on its own: that description_max_chars caps `details` specifically, and that strip_html controls whether details come back as HTML.

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 a specific verb and resource with scope and ordering: 'One group's polls, newest first: 1 call.' It is immediately distinguishable from siblings like get_poll (single poll), create_poll, and list_groups.

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?

Explicitly routes the agent away from a tempting wrong path: 'For member activity use get_participation_report, not this plus list_memberships.' That is a clear when-not plus a named alternative, though it covers only this one scenario and says nothing about paging or when to prefer get_poll.

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

Deploy Server

Other Tools