HAOps MCP Server

haops_delete_message

Delete a message permanently from a discussion thread. Only the message author can delete.

Instructions

Delete a message from a discussion thread. Only the message author can delete. This is permanent.

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": {
      "projectSlug": "<projectSlug>",
      "discussionId": "<discussionId>",
      "messageId": "<messageId>"
    },
    "name": "haops_delete_message"
  }
}

Input Schema

Name	Required	Description
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`messageId`	Yes	UUID of the message to delete
`projectSlug`	Yes	The project slug (URL identifier)
`discussionId`	Yes	UUID of the discussion thread

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses two key behavioral traits: the action is permanent and only executable by the message author. This is sufficient for a delete operation, though it does not detail side effects like cascade deletions.

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 two sentences with no wasted words. It front-loads the purpose and then adds constraints. Every sentence adds essential information.

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?

Given the tool has no output schema and four well-documented parameters, the description provides enough context: the action, the required permissions, and the permanence. The sibling tools cover other delete operations, so the differentiation is clear.

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?

The input schema already provides descriptions for all four parameters (100% coverage), so the baseline is 3. The description does not add any parameter-specific meaning beyond what the schema provides; it only contextualizes the overall operation.

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 clearly states the verb 'delete' and the resource 'message from a discussion thread', and distinguishes it from sibling tools like haops_delete_discussion or haops_delete_channel by specifying the context (discussion thread). It also adds constraints (only author, permanent).

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?

The description explicitly states a prerequisite (only message author can delete) and the permanent nature, giving clear context for when to use. It does not explicitly mention when not to use or alternatives, but the sibling list includes haops_edit_message for editing, and the constraint implicitly guides usage.

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

Deploy Server