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_versions

Retrieve all available versions and distribution tags for any Homebridge plugin by providing its npm package name.

Instructions

Get available versions and dist-tags for a specific Homebridge plugin.

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_versions"
  }
}

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

A3.5/5.0
Behavior3/5

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

Without annotations, the description carries the full burden. It implies a read operation and mentions the resource, but does not disclose any potential side effects, response format, or additional behavioral traits. For a simple tool, this is adequate but not thorough.

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, front-loaded with the key information, and contains no unnecessary words. Every word serves a purpose.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally complete. However, it lacks context on the return value and usage guidance relative to siblings, which would help the agent use it correctly.

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?

The schema has 100% coverage with a clear description for pluginName. The tool description adds no extra meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Get' and the resource 'available versions and dist-tags for a specific Homebridge plugin'. It distinguishes itself from sibling tools like get_plugin_changelog or get_plugin_config_schema by specifying versions and dist-tags.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Among 20 sibling tools, there are several other 'get_*' tools, but the description does not mention when this one is appropriate or when another should be used.

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