HAOps MCP Server

haops_delete_doc_section

Delete a section from a documentation artifact by specifying the project, artifact, and section slugs.

Instructions

Delete a section from a documentation artifact.

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>",
      "artifactSlug": "<artifactSlug>",
      "sectionSlug": "<sectionSlug>"
    },
    "name": "haops_delete_doc_section"
  }
}

Input Schema

Name	Required	Description
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`projectSlug`	Yes	The project slug (URL identifier)
`sectionSlug`	Yes	The section slug to delete
`artifactSlug`	Yes	The doc artifact slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided. The description merely says 'Delete' without detailing side effects, permission requirements, reversibility, or whether it's a soft or hard delete. For a destructive action, this is insufficient.

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?

A single, front-loaded sentence with no extraneous words. Every word earns its place.

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?

No output schema is present. The description lacks important context for a deletion tool, such as return value format, error conditions, or impact on related entities. Given the destructive nature, more completeness is expected.

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%, with each parameter described (projectSlug, artifactSlug, sectionSlug, verbose). The description adds no additional parameter meaning beyond what the schema provides. Baseline 3 applies.

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 section from a documentation artifact,' using a specific verb and resource. It distinguishes from sibling delete tools like haops_delete_doc_artifact and haops_delete_help_section by specifying 'doc section'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like haops_update_doc_section or haops_delete_doc_artifact. The description lacks context about prerequisites or scenarios where deletion is appropriate.

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

Deploy Server