Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete category

labels_delete_category
DestructiveIdempotent

Delete a category from a registry scope in Home Assistant by scope and category ID. Use when a category is no longer needed within its scope.

Instructions

Delete a category from a registry scope.

Calls WS config/category_registry/delete with scope and category_id and returns Home Assistant's result unchanged.

Use when: a category is no longer needed within its scope. Returns: dict with scope, category_id, the raw WS result, and ok. Errors: on a WS failure, returns {"scope": ..., "category_id": ..., "ok": false, "error": "<message>"}.

Input Schema

NameRequiredDescriptionDefault
scopeYesRegistry scope the category belongs to, e.g. 'automation'.
category_idYesCategory registry ID to delete; obtain it from labels_list_categories.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.25.1
    • addedInput schema / properties / category_id / description
      Added value: +"Category registry ID to delete; obtain it from labels_list_categories."
    • addedInput schema / properties / scope / description
      Added value: +"Registry scope the category belongs to, e.g. 'automation'."
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the WS call path, success dict shape, and explicit failure return shape, which are useful behavioral details 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.

Conciseness4/5

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

Front-loads the purpose, then separates call, usage, return, and error details with line breaks. It is mostly efficient, though some return/error detail is redundant given an output schema exists.

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?

With rich annotations, full schema coverage, and an output schema, the description supplies the remaining operational context: when to use it, success shape, and failure shape. It is complete enough for correct invocation.

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 input schema already explains scope examples and where to obtain category_id. The description only restates the two parameter names, adding no semantics beyond structured data.

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 ('Delete a category') and scope ('from a registry scope'), separating it from sibling label/category operations such as labels_delete_label. An agent can identify the operation without opening the 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?

Explicitly says 'Use when: a category is no longer needed within its scope,' giving a clear trigger condition. It does not name alternatives or exclusions, so it falls short of full when/when-not guidance.

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