Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_delete_feature

Delete a feature from a HAOps module. Requires confirmation to cascade delete child issues.

Instructions

Delete a feature from a HAOps module. If the feature has child issues, requires confirm=true to cascade delete.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true to confirm cascade deletion of child issues. Required if feature has children.
verboseNoIf true, return the full API response instead of the compact summary (default: false)
featureIdYesUUID of the feature to delete
projectSlugYesThe project slug (URL identifier)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.7/5.0
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 discloses the cascade deletion behavior and the need for confirmation, but does not mention irreversibility, required permissions, or error handling. The behavioral disclosure is partial.

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 concise sentences, front-loading the core action. Every sentence adds value without redundancy.

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

Completeness3/5

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

Given no output schema, the description does not explain return values or success/failure signaling. It covers the cascade condition but lacks details on what happens if confirm is false when children exist, or what the output looks like.

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 description coverage is 100%, so baseline is 3. The description reinforces the confirm parameter's role in cascade deletion but does not add significant new meaning beyond what the schema already provides.

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 'Delete a feature from a HAOps module', which is a specific verb+resource. It differentiates from sibling tools like haops_create_feature or haops_delete_module by focusing on feature deletion.

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 mentions the condition for cascade deletion (confirm=true when child issues exist) but does not provide explicit when-to-use or when-not-to-use guidance relative to alternatives. It lacks context for choosing this tool over related delete tools.

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

Deploy Server

Other Tools