Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_create_discussion

Create a discussion thread in a HAOps project, optionally linked to a Module, Feature, or Issue, or placed in a specific channel with a first message.

Instructions

Create a discussion thread in a HAOps project. Two modes: (1) Entity-linked — provide discussableType + discussableId to link to a Module/Feature/Issue (no channelId needed). (2) Channel-based — provide channelId (use haops_list_channels to find it). Can combine both. At least one of channelId or discussableType+discussableId is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoDiscussion type (optional, default: general)
titleYesDiscussion title
verboseNoIf true, return the full API response instead of the compact summary (default: false)
priorityNoPriority level (optional)
channelIdNoUUID of the channel. Required for channel-based discussions. Use haops_list_channels to get valid channel UUIDs.
projectSlugYesThe project slug (URL identifier)
firstMessageNoInitial message content for the discussion thread (optional). Use markdown formatting for best results.
discussableIdNoUUID of the entity to link the discussion to. Required together with discussableType for entity-linked discussions.
discussableTypeNoEntity type to link the discussion to. For entity-linked discussions, provide both discussableType and discussableId (no channelId needed).
firstMessageContentTypeNoContent format for firstMessage (optional, default: markdown). Markdown is recommended for agents.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the two modes but does not disclose behavioral traits like return value, side effects, authentication requirements, or error handling for a creation operation.

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 concise and well-structured, presenting the two modes in a clear, front-loaded manner with no wasted sentences.

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?

Given the tool's complexity (10 parameters, two modes, no output schema), the description adequately covers the essential usage patterns. It lacks detail on the return value but is otherwise complete for creating a discussion.

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 has 100% description coverage for all parameters. The description adds context about the two usage modes, but beyond that, the parameter documentation is already detailed in the schema, so the description adds minimal additional semantic value.

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 'Create a discussion thread in a HAOps project' and explains two distinct modes (entity-linked and channel-based), which differentiates it from sibling tools like haops_get_discussion or haops_delete_discussion.

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 provides explicit guidance on when to use each mode and references haops_list_channels for obtaining a channelId. It clarifies that at least one of channelId or discussableType+discussableId is required, but does not explicitly state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tbranzov/haops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server