Skip to main content
Glama
Sign In
@mp-consulting/homebridge-mcp-server

@mp-consulting/homebridge-mcp-server

by mp-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_accessory

Retrieve detailed information about a specific home accessory using its unique identifier. First use list_accessories to find the uniqueId.

Instructions

Get detailed information about a specific accessory by its uniqueId. Use list_accessories first to find the uniqueId.

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": {
      "uniqueId": "<uniqueId>"
    },
    "name": "get_accessory"
  }
}

Input Schema

NameRequiredDescriptionDefault
uniqueIdYesThe unique identifier of the accessory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read operation via 'Get detailed information' but does not state read-only, permissions, or expected response structure. Adequate but not fully transparent.

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, front-loaded with the core purpose, and no extraneous information.

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?

No output schema, so description should hint at response content. It vaguely says 'detailed information' without specifics. For a simple single-param tool, it's adequate but not complete.

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% with clear description. The description adds value by explaining how to obtain the uniqueId parameter via list_accessories, which goes beyond the schema.

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 action: 'Get detailed information about a specific accessory by its uniqueId.' Distinguishes from sibling tools like list_accessories and set_accessory.

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 instructs to 'Use list_accessories first to find the uniqueId,' guiding the agent on prerequisite steps and which sibling to use for discovery.

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