HAOps MCP Server

haops_search_discussion

Search messages within a discussion thread using a query. Returns matching messages for the specified project and discussion.

Instructions

Search messages within a specific discussion thread. Returns matching messages for the given query.

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

Input Schema

Name	Required	Description
`query`	Yes	Search query string
`projectSlug`	Yes	The project slug (URL identifier)
`discussionId`	Yes	UUID of the discussion to search

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it returns matching messages but lacks details on pagination, limits, permissions, or error behavior. For a search tool, this is insufficient transparency.

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?

Two short, efficient sentences with no excess words. Ideal conciseness.

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 3 required params, the description is minimal. It does not explain return format, error cases, or how to effectively use the tool. Sibling differentiation is thin.

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 100%, so parameters are fully described in the schema. The description does not add extra meaning beyond the schema (e.g., query format, how to derive projectSlug/discussionId). Baseline 3 is appropriate.

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 'Search messages within a specific discussion thread' and the resource 'messages within a discussion', distinguishing it from siblings like haops_get_discussion (thread metadata) or haops_get_discussion_messages (all messages).

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?

The description implies usage for searching messages in a thread but does not explicitly state when to use this tool vs alternatives like haops_get_discussion_messages or haops_search_help. No when-not or exclusions are provided.

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

Deploy Server