@mp-consulting/homebridge-mcp-server

Overview Schema Source Related Servers Discussions Admin

remove_cached_accessory

Remove a stale cached accessory from Homebridge by providing its UUID. Use this to clean up orphaned or outdated accessories.

Instructions

Remove a specific cached accessory by its UUID. Useful for cleaning up stale accessories.

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

Input Schema

Name	Required	Description	Default
`uuid`	Yes	The UUID of the cached accessory to remove

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.5Jul 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It states the action but discloses no behavioral traits such as whether removal is permanent, the effect on other data, error handling for invalid UUIDs, or safety considerations.

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 sentences, no unnecessary words. The action is front-loaded, and the purpose is immediately clear. Every sentence adds value.

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

Completeness3/5

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

For a single-parameter tool without output schema, the description is adequate but incomplete. It does not mention return values or success/failure indicators, which are helpful for an agent to interpret results.

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%, so the schema already documents the 'uuid' parameter. The description adds 'by its UUID', which restates the schema purpose without adding new semantics like format or constraints.

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 clearly states the verb 'Remove', the object 'cached accessory', and the method 'by its UUID'. It also provides a use case ('cleaning up stale accessories'), making it distinct from siblings like 'reset_cached_accessories'.

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 implies usage for removing stale accessories but does not explicitly state when to use this tool versus alternatives (e.g., 'reset_cached_accessories' for bulk removal). No exclusions or when-not-to-use guidance is provided.

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