Skip to main content
Glama

Delete hierarchy

delete_hierarchy
DestructiveIdempotent

Permanently deletes a hierarchy by ID while preserving its blueprints in your account as unlinked items.

Instructions

Permanently delete one of your hierarchies. The blueprints in it are not deleted: they stay in your account, unlinked from any hierarchy.

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

Input Schema

NameRequiredDescriptionDefault
idYesHierarchy id, e.g. ha_clx1abc.

Output Schema

NameRequiredDescriptionDefault
messageNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"ID of the hierarchy to delete"New value: +"Hierarchy id, e.g. ha_clx1abc."
    • addedInput schema / properties / id / maxLength
      Added value: +128
    • addedInput schema / properties / id / pattern
      Added value: +"^[A-Za-z0-9][A-Za-z0-9_-]{0,127}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as destructive and idempotent, but the description adds important non-obvious behavior: deletion is permanent and contained blueprints remain in the account unlinked from any hierarchy. It does not cover permissions or confirmation behavior, but it provides meaningful context beyond the annotations.

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?

Two short sentences with zero waste. The core action is front-loaded, and the second sentence immediately clarifies the non-cascade effect.

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

Completeness5/5

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

For a one-parameter destructive tool with rich annotations and an output schema, the description is complete enough. It states the permanent effect and the treatment of contained blueprints, which are the key behavioral details an agent needs.

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%, and the single id parameter is documented with an example. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: permanently delete a hierarchy. It also clarifies that blueprints are not deleted, which distinguishes this from delete_blueprint and related sibling tools.

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 makes the operation understandable, but it does not explicitly state when to use this tool versus delete_blueprint, update_blueprint, or other alternatives. The blueprint-retention note implies a distinction, but the agent must infer it.

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