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_plugin_config_schema

Get the configuration schema for any Homebridge plugin to learn how to configure it in Homebridge.

Instructions

Get the config.schema.json for a plugin, which describes how to configure it in Homebridge.

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": {
      "pluginName": "<pluginName>"
    },
    "name": "get_plugin_config_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginNameYesThe npm package name of the plugin (e.g. 'homebridge-hue')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It states 'Get' which implies read-only, and describes the retrieval of a schema file. It does not elaborate on authentication or side effects, but for a read operation it is sufficiently 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?

The description is a single sentence with no wasted words. It front-loads the action and resource, making it efficient and easy to parse.

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 simple retrieval tool with one fully-described parameter and no output schema, the description provides all necessary context to understand the tool's purpose and usage.

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 description adds no additional meaning beyond the schema description for the parameter. Baseline 3 is appropriate as the schema already documents the parameter well.

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 specifies the verb 'Get' and resource 'config.schema.json for a plugin' and explains its purpose ('describes how to configure it in Homebridge'). It clearly distinguishes from siblings like get_config or get_plugin_changelog.

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 when to use (to get configuration schema for a plugin) but provides no explicit guidance on when not to use or alternatives. Given the tool's simple nature, it is adequate but lacks explicit usage context.

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