Skip to main content
Glama
loomiomcp
by soil-dev

get_discussion

Read-onlyIdempotent

Fetch a single Loomio discussion by numeric ID or short key to get its full body, topic ID, counters, and URL. Include thread items optionally, with item limits and next-offset paging details.

Instructions

One discussion by numeric id or short key: 1 call (2+ with include_items). Returns the full body, topic_id, counters, url; include_items: true embeds list_thread_items as thread_items (items_limit; next_offset says when to page on). Prose: get_thread_markdown; a group's threads: list_discussions.

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": {
      "id_or_key": "<id_or_key>"
    },
    "name": "get_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_keyYesDiscussion id or short key.
strip_htmlNoPlain text instead of HTML; default false.
items_limitNoWith include_items: items to embed (default 200, max 1000).
include_itemsNoAlso embed the thread's items as `thread_items` (+1 call per 500 items).
items_body_max_charsNoWith include_items: chars per body (default 4000; 0 omits, -1 full).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / id_or_key / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[A-Za-z0-9_-]+$",
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
  2. Changed1 schema field changedv0.0.16
    • changedInput schema / properties / include_items / description
      Previous value: -"Also embed the thread's items as `thread_items` (+1 call)."New value: +"Also embed the thread's items as `thread_items` (+1 call per 500 items)."
  3. Addedv0.0.13
  4. Removedv0.0.10
  5. First observedv0.0.6

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare the operation read-only, idempotent, open-world, and non-destructive. The description adds useful behavior beyond annotations: returned fields, embedding thread_items, pagination via next_offset, and call-count implications of include_items.

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?

The description is compact and front-loaded, starting with the resource and lookup key. Every clause contributes routing, return-shape, or paging information without filler.

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 carries the return-value explanation and does so clearly: full body, topic_id, counters, url, embedded thread_items, and next_offset paging. Combined with complete schema descriptions and safety annotations, an agent has enough context 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 100%, so the baseline is 3, but the description adds meaning beyond the schema for id_or_key, include_items, and items_limit. It does not explain strip_html or items_body_max_chars in prose, but those remain fully documented in the schema.

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?

The description states a specific verb and resource: retrieve one discussion by numeric id or short key. It also distinguishes itself from siblings by naming get_thread_markdown for prose and list_discussions for group threads.

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?

It explicitly routes the agent to alternatives: get_thread_markdown for prose and list_discussions for a group's threads. It also explains when to use include_items to embed thread items, making the selection logic clear.

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