Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete an automation config

automations_delete_automation
DestructiveIdempotent

Permanently delete a Home Assistant automation by config id and reload automations. Requires confirm=True; otherwise returns a safety prompt.

Instructions

Delete an automation by config id, then reload automations.

Without confirm=True returns a safety prompt; with confirm=True deletes /api/config/automation/config/<id> and calls the automation.reload service.

Returns: dict {"status": "deleted", "automation_id", "result"}. Errors: returns {"error": "confirmation_required", "message": ..., "action": ...} when confirm is not True, or {"error": "not found", "automation_id": aid} when no automation has that config id. Limits: requires confirm=True; deletion is immediate and permanent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be True to actually delete the automation. False (default) returns a safety prompt instead of deleting anything.
automation_idYesAutomation config id to delete — the entity's `id` attribute, not its entity_id. A leading 'automation.' is stripped if present.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.25.1
    • addedInput schema / properties / automation_id / description
      Added value: +"Automation config id to delete — the entity's `id` attribute, not its entity_id. A leading 'automation.' is stripped if present."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be True to actually delete the automation. False (default) returns a safety prompt instead of deleting anything."
  2. Changed1 schema field changedv0.18.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  3. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds material context beyond them: the two-step confirm safety gate, the side effect of calling automation.reload, the concrete endpoint, exact error shapes for confirmation_required and not found, and the irreversibility warning ('deletion is immediate and permanent').

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?

Front-loads the action and the confirm gate, then uses labeled Returns/Errors/Limits blocks. Slight redundancy with the output schema, but every line carries actionable content and the structure is easy to scan.

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 2-param tool with full schema coverage, annotations, and an output schema, this covers the remaining gaps (confirmation workflow, error responses, permanence) thoroughly. Nothing an agent needs to call it correctly is missing.

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 both parameters are already documented in the schema (confirm's safety behavior and automation_id's config-id/prefix rules). The description largely restates those semantics rather than adding new ones, so the baseline 3 applies.

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+resource+scope: 'Delete an automation by config id, then reload automations.' An agent can distinguish this from automations_delete_script, automations_delete_scene, and the get/set config siblings without opening any schema.

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

Usage Guidelines4/5

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

Clearly describes the confirm-gated workflow (without confirm=True you get a safety prompt; with it the deletion runs), which is the key usage condition. It stops short of naming alternatives (e.g. disable_automation vs delete) or when deletion is inappropriate, so it is clear context without explicit routing.

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