Skip to main content
Glama
soil-dev

loomiomcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_discussions

Read-onlyIdempotent

Fetch a group's discussions with newest activity first, filter by open or closed status, and control body length or HTML stripping for readable results.

Instructions

One group's discussions, newest activity first: 1 call. status defaults to 'open'; description_max_chars (default 1500) caps bodies, description_truncated: true marking a cut; strip_html (default true) gives plain text. Every visible group: list_threads; keywords: search_content. Subgroups are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1-200. Default 50.
offsetNoPage offset. Default 0.
statusNo'open' (default) = unlocked, 'closed' = locked, 'all'.
group_idYes
strip_htmlNoPlain text instead of HTML; default true.
description_max_charsNoChars per `description`; 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 `description`; 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 discussions 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 by status. 'open' = unlocked, 'closed' = locked, 'all' = every kept discussion. Loomio defaults to 'open'."New value: +"'open' (default) = unlocked, 'closed' = locked, 'all'."
    • addedInput schema / properties / strip_html
      Added value: +{
+  "description": "Plain text instead of HTML; default true.",
+  "type": "boolean"
+}
  2. First observedv0.0.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is clear. The description adds behavioral details: default status filtering, pagination hints via '1 call', and default strip_html. However, return format and pagination behavior are only partially addressed. Baseline 3 appropriate given annotations carry the core traits.

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?

Efficient and front-loaded: the primary purpose and scoping are stated first, followed by parameter defaults and related tools. No wasted words. Could be tightened further but is well structured.

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?

For a list tool with annotations covering safety and schema covering most parameters, the description provides useful defaults and scoping. However, it does not mention pagination behavior (offset/limit interaction) or return structure, and there is no output schema. Adequate but incomplete for an agent needing to call correctly.

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 83%, so most parameters are already described. The description adds behavioral nuance for status default, description_max_chars truncation behavior (with description_truncated flag), and strip_html default, which goes beyond schema. This is slightly above baseline but not rich enough for a 4.

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?

States a specific verb+resource ('One group's discussions') and a scope constraint (subgroups excluded). Does not explicitly name the related sibling get_discussion or list_threads, though it does reference list_threads in a different context. Distinguishable from siblings but not maximally so.

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?

Names alternatives: 'Every visible group: list_threads' and 'keywords: search_content', giving clear when-to-use context for related tasks. Lacks explicit when-not or differentiation from get_discussion / list_polls. Adequate but not comprehensive.

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