Skip to main content
Glama
loomiomcp
by soil-dev

delete_discussion

DestructiveIdempotent

Discard a discussion by ID or key via soft delete: it leaves all lists and blanks its text, but a group admin can restore it. Use update for text corrections.

Instructions

Discard a discussion by id_or_key: 1 call. Loomio's SOFT delete: it leaves every list and its text is blanked, but nothing is permanently erased (a group admin can restore it). For a text mistake prefer update_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": {
      "id_or_key": "<id_or_key>"
    },
    "name": "delete_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_keyYesDiscussion id or short key.

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. Addedv0.0.13

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by explaining that this is a SOFT delete: removed from lists, text blanked, but recoverable by a group admin. That is exactly the consequence information an agent needs before invoking a destructive tool, and it is consistent with the annotations.

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?

Two tight sentences, front-loaded with the action and identifier, followed by consequence then alternative. The fragment '1 call' is filler that doesn't earn its place, but nothing else is wasted.

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?

For a single-parameter destructive tool with no output schema, the definition supplies what matters: reversibility, visibility effect (blanked text, removed from lists), restore path, and the safer alternative. Nothing needed to call it correctly is missing.

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 already 100% and documents 'Discussion id or short key', so the description only restates the parameter name by reference. The odd '1 call' phrase adds no semantic content about the identifier format; baseline 3 applies.

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 ('Discard a discussion') plus the identifier it operates on, and names update_discussion as the contrasting tool. An agent can distinguish it from create_discussion/update_discussion/list_discussions 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes text corrections to update_discussion ('For a text mistake prefer update_discussion'), giving a clear alternative with its selecting condition. It doesn't cover other when-not cases (e.g. discussions with replies, or delete_comment delegation), but the key fork is spelled out.

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