Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_deprecate_skill

Soft-delete a skill and deprecate it across all versions, preserving history for audit. Returns confirmation with version count.

Instructions

Soft-delete + deprecate a skill (DELETE /api/skills/[name]). Cascades the soft-delete across ALL versions (current + historical) and flips isDeprecated=true on the current row. History remains visible via /api/skills/[name]/history for audit context. Admin-only, gated by ENABLE_COMPOSED_PROTOCOLS. Returns {message, versionCount}.

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

Input Schema

NameRequiredDescriptionDefault
nameYesKebab-case skill name to soft-delete.
scopeNoScope of the target skill. Defaults to "system".
verboseNoIf true, return the full API response instead of the compact summary (default: false)
projectSlugNoProject slug — REQUIRED when scope="project"; MUST be omitted when scope="system".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description fully carries the transparency burden. It discloses soft-delete vs. hard-delete, cascading across all versions, toggling isDeprecated=true, preservation of history via a separate endpoint, admin-only restriction, feature flag dependency, and the return structure ({message, versionCount}).

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?

Three sentences with no redundant words. Key information is front-loaded (soft-delete and deprecate), followed by cascading behavior, history visibility, access control, and return type. Every sentence adds distinct value.

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?

The description covers the main behavioral aspects (cascade, soft-delete, history, admin, return). Lacks error scenarios or rate limits, but the complexity is well addressed. Return structure is specified despite no output schema.

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% (all parameters documented), so baseline is 3. The description adds value by explaining cascade behavior and specifying name as kebab-case, but does not elaborate on scope, verbose, or projectSlug beyond schema comments.

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 explicitly states 'soft-delete + deprecate a skill', specifies the API endpoint, and details cascading behavior across all versions with a return value. It clearly distinguishes from sibling deprecate tools like haops_deprecate_role_template and haops_deprecate_skill_pack.

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 identifies admin-only access and a feature flag gate, but does not explicitly compare with alternatives such as haops_transition_skill or haops_delete_skill. Usage context (when to deprecate vs. delete or update) is implied but not systematically stated.

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