Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_delete_doc_artifact

Delete a documentation artifact and all its sections from a project. Provide the project slug and artifact slug to remove the artifact permanently.

Instructions

Delete a documentation artifact and all its sections.

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

Input Schema

NameRequiredDescriptionDefault
verboseNoIf true, return the full API response instead of the compact summary (default: false)
projectSlugYesThe project slug (URL identifier)
artifactSlugYesThe doc artifact slug to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.5/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 the full burden. It states the tool deletes an artifact and its sections but does not disclose if the action is irreversible, requires special permissions, or has cascading effects. For a destructive operation, more behavioral context is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and directly states the action. Could benefit from a brief additional context, but no wasted words. Front-loading is good as the verb 'Delete' appears first.

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?

For a simple delete operation with no output schema and 3 well-documented parameters, the description covers the essential information. Minor gaps like irreversibility or permissions prevent a perfect score.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter.

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 target resource (documentation artifact), and scope (all its sections). It distinguishes itself from sibling tools like haops_delete_doc_section which deletes only a single section.

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?

No explicit guidance on when to use this tool versus alternatives like haops_delete_doc_section. However, the purpose is clear enough that an agent can infer usage context, but explicit when-to-use or when-not-to-use would improve score.

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