Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_delete_help_section

Delete a help center section and all its articles. Restricted to admin users.

Instructions

Delete a help center section and all its articles. Admin-only.

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": {
      "sectionSlug": "<sectionSlug>"
    },
    "name": "haops_delete_help_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
verboseNoIf true, return the full API response instead of the compact summary (default: false)
sectionSlugYesThe help section slug to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that deleting a section cascades to all its articles, and that the action is restricted to admins. However, it does not mention that the action is irreversible, whether dependencies exist, or what happens on failure. This is adequate but not fully transparent.

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 extremely concise: two short sentences that immediately communicate the core action, scope, and access restriction. Every word adds value, and there is no fluff. It is front-loaded with the most critical information.

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 low complexity (two parameters, no output schema, no nested objects), the description adequately covers the primary behavior. It states that the section and all its articles are deleted and that admin privileges are required. However, it could be improved by mentioning that the action is irreversible and suggesting that users should verify the section slug beforehand (e.g., via haops_list_help_sections). Still, it is largely complete for its simplicity.

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 the baseline is 3. The description does not add any information about the parameters beyond what the schema already provides. The `verbose` parameter's purpose is fully explained in the schema, and `sectionSlug` is self-explanatory. No additional context is provided.

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 action ('Delete'), the resource ('help center section'), and the scope ('and all its articles'), with a specific access requirement ('Admin-only'). It distinguishes itself from sibling tools like haops_delete_help_article by focusing on sections and their contained articles.

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?

The description does not provide any guidance on when to use this tool versus alternatives. There is no mention of prerequisites, potential side effects, or scenarios where other tools (e.g., deleting individual articles first) might be preferred. The only hint is 'Admin-only', which implies authorization but not usage context.

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