Skip to main content
Glama
loomiomcp
by soil-dev

create_comment

Post a comment to a Loomio discussion or reply within an existing thread by providing the comment body and a target discussion or parent item.

Instructions

Post a comment in a thread: 1 call (2 when discussion_id is a short key). Required body (+ body_format: 'html' for HTML; Loomio stores an omitted format as Markdown) and a target: discussion_id for a top-level comment, or parent_id + parent_type ('Comment' for a threaded reply; 'Poll' / 'Stance' / 'Outcome'). A new thread: create_discussion.

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": {
      "body": "<body>"
    },
    "name": "create_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
parent_idNoComment, Poll, Stance or Outcome id to reply to (needs parent_type).
body_formatNoDefault 'md'; 'html' when `body` is HTML.
parent_typeNoType of parent_id; required with it.
discussion_idNoDiscussion id or short key (+1 call) for a top-level comment; or use parent_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / discussion_id / 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. Changed10 schema fields changedv0.0.13
    • removedInput schema / properties / body / description
      Removed value: -"Comment body (required)."
    • changedInput schema / properties / body_format / description
      Previous value: -"Format of `body`. Defaults to Loomio's group default when omitted."New value: +"Default 'md'; 'html' when `body` is HTML."
    • addedInput schema / properties / discussion_id / anyOf
      Added value: +[
      +  {
      +    "pattern": "^[A-Za-z0-9_-]+$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
    • changedInput schema / properties / discussion_id / description
      Previous value: -"ID of the discussion to comment on."New value: +"Discussion id or short key (+1 call) for a top-level comment; or use parent_id."
    • removedInput schema / properties / discussion_id / exclusiveMinimum
      Removed value: -0
    • removedInput schema / properties / discussion_id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / discussion_id / type
      Removed value: -"integer"
    • addedInput schema / properties / parent_id
      Added value: +{
      +  "description": "Comment, Poll, Stance or Outcome id to reply to (needs parent_type).",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / parent_type
      Added value: +{
      +  "description": "Type of parent_id; required with it.",
      +  "enum": [
      +    "Discussion",
      +    "Comment",
      +    "Poll",
      +    "Stance",
      +    "Outcome"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "discussion_id",
      -  "body"
      -]New value: +[
      +  "body"
      +]
  3. 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 the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real context beyond them: a call-cost disclosure ('1 call, 2 when discussion_id is a short key') and the non-obvious storage rule that an omitted `body_format` is persisted as Markdown. It does not cover permissions or error behavior, which is why it stops 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?

Dense but well front-loaded — the call-cost note and required `body` come first, then the branching target rules. A few compact formulations ('1 call (2 when `discussion_id` is a short key)') are slightly cryptic on first read but earn their space.

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?

For a 5-parameter mutation tool with annotations but no output schema, the description covers targeting, format, cost and the sibling alternative. It omits what the call returns (e.g., the new comment id) and any permission requirements, which keeps it from being fully complete.

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 80%, so baseline is 3, but the description adds genuine meaning: what 'html' means for `body_format`, the Markdown-storage default, and the reply-type semantics of `parent_type` ('Comment' for threaded replies, Poll/Stance/Outcome). Minor gap: the schema enum also allows 'Discussion' as a `parent_type`, which the prose list omits, leaving a small ambiguity.

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 ('Post a comment in a thread') and immediately scopes it against the sibling create_discussion for new threads. An agent can distinguish it from create_discussion, update_comment and delete_comment without opening a schema.

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 names the two call shapes — `discussion_id` for a top-level comment versus `parent_id` + `parent_type` for a threaded reply — and routes the new-thread case to create_discussion. Both the when and the alternative are stated, not implied.

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