Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Remove Zone

ha_remove_zone
DestructiveIdempotent

Delete a Home Assistant zone by zone ID or entity ID to remove unused zones; verify the ID first and avoid removing zones used in automations.

Instructions

Remove a Home Assistant zone.

EXAMPLES:

  • Remove zone: ha_remove_zone("office")

  • Remove by entity_id: ha_remove_zone("zone.office")

WARNING: Removing a zone used in automations may cause those automations to fail. Use ha_get_zone() to find the zone_id for the zone you want to remove.

NOTE: Zones defined in YAML, and the home zone, cannot be removed here.

If a Claude Desktop user gets a 4-minute timeout with no result on this call, read the target back before repeating it, and tell them to wait a few seconds before clicking the manual-approve button, as clicking it too quickly is known to cause hangs in Claude Desktop. This workaround is specific to Claude Desktop.

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait for the zone to be gone before returning. Set to False for bulk operations.
zone_idYesZone ID or entity_id of the zone to remove

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.0.0
    • addedInput schema / properties / wait
      Added value: +{
+  "default": true,
+  "description": "Wait for the zone to be gone before returning. Set to False for bulk operations.",
+  "type": "boolean"
+}
    • changedInput schema / properties / zone_id / description
      Previous value: -"Zone ID to remove"New value: +"Zone ID or entity_id of the zone to remove"
  2. Changed1 schema field changedv8.6.0
    • changedInput schema / properties / zone_id / description
      Previous value: -"Zone ID to remove (use ha_get_zone to find IDs)"New value: +"Zone ID to remove"
  3. First observedv7.14.2

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the destructiveHint/idempotentHint annotations by naming the collateral risk (automations referencing the zone may fail) and the hard restrictions (YAML zones and home zone are not removable). The Claude Desktop timeout note adds an operational caveat that annotations cannot carry, though it is idiosyncratic and does not describe the returned result — which the output schema covers anyway.

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?

Purpose is front-loaded, and the EXAMPLES/WARNING/NOTE blocks are terse and scannable. The closing Claude Desktop paragraph is the weakest element — three sentences of client-specific debugging detail that dilute the otherwise tight structure.

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 destructive, idempotent single-entity removal with full schema coverage, annotations, and an output schema, nothing an agent needs is missing: identifier resolution, failure modes, and prohibited targets are all present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds value by showing concrete accepted formats ("office" vs "zone.office"), clarifying that zone_id is polymorphic. The `wait` flag is left entirely to the schema, which documents it adequately.

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?

States a specific verb and resource ("Remove a Home Assistant zone") that is immediately distinguishable from siblings ha_get_zone and ha_set_zone. The examples show the two accepted identifier forms, so the agent knows exactly what this tool consumes.

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

Usage Guidelines5/5

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

Explicitly routes the agent to ha_get_zone() to resolve a zone_id, and states two concrete exclusion cases where the tool must not be used (YAML-defined zones and the home zone). Both positive usage and when-not-to-use are covered.

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