HAOps MCP Server

haops_get_discussion_messages

Retrieve paginated messages from a discussion thread to read conversation context before responding.

Instructions

Retrieve messages from a discussion thread with pagination. Essential for reading conversation context before responding.

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>"
    },
    "name": "haops_get_discussion_messages"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1)
`limit`	No	Messages per page (default: 50, max: 100)
`projectSlug`	Yes	The project slug (URL identifier)
`discussionId`	Yes	UUID of the discussion

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions pagination but does not cover ordering, response format, side effects (read-only assumed but not stated), rate limits, or authentication. Minimal behavioral context.

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 concise sentences with the primary action front-loaded. No wasted words, but could be slightly more efficient without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 4 parameters, the description lacks details on ordering, how to paginate (next page links?), returned fields, and error conditions. Incomplete for full understanding of tool behavior.

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 descriptions cover all 4 parameters (100% coverage). Description adds 'with pagination' hinting at page/limit but no additional meaning beyond what schema provides. Baseline 3 applies.

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?

Clearly states the tool retrieves messages from a discussion thread with pagination. The phrase 'Essential for reading conversation context before responding' adds purpose context. Slightly generic but distinguishes from siblings like get_discussion or post_message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Implies usage before responding to a discussion, but does not explicitly mention when not to use it or list alternatives. No guidance on prerequisites or relationship to other tools like get_discussion.

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

Deploy Server