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_changelog

Retrieve the changelog content for any installed Homebridge plugin to review version history and changes.

Instructions

Get the CHANGELOG.md content for an installed 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_changelog"
  }
}

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

B3.3/5.0
Behavior2/5

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

With no annotations, the description alone must disclose behavior, but it only states the basic function without mentioning what happens if the plugin lacks a changelog, performance implications, or error conditions.

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, front-loaded sentence with no unnecessary words, efficiently conveying the tool's 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?

For a simple retrieval tool with one parameter and no output schema, the description is adequate but leaves uncertainty about edge cases (e.g., missing changelog) and does not specify the return format.

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 already provides a complete description of 'pluginName' (100% coverage), so the description adds only minor context by specifying 'installed' and an example, meeting the baseline for high coverage.

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 tool's action ('Get') and resource ('CHANGELOG.md content for an installed Homebridge plugin'), distinguishing it from sibling tools that retrieve other types of information.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_plugin_versions' or 'lookup_plugin', nor does it mention prerequisites or exclusions.

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