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

@mp-consulting/homebridge-mcp-server

by mp-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lookup_plugin

Find details about a Homebridge plugin by entering its npm package name. Get description, version, and other metadata.

Instructions

Get detailed information about a specific Homebridge plugin from the npm registry.

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": "lookup_plugin"
  }
}

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.7/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility. It only states it gets info from npm registry, which is read-only, but omits details like rate limits, authentication, or what 'detailed information' includes.

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?

Single sentence that immediately communicates the tool's purpose. No unnecessary words.

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?

The tool is simple with one parameter, but the description is vague about what 'detailed information' contains. Without an output schema, it should hint at fields like version or author.

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?

The schema covers 100% of parameters, and the description adds an example and clarifies the parameter is the npm package name, adding value 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 clearly states the verb 'Get', the resource 'detailed information about a specific Homebridge plugin', and the source 'from the npm registry'. This distinguishes it from sibling tools like search_plugins and list_plugins.

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 when detailed info on a specific plugin is needed, but does not explicitly contrast with sibling tools or provide when-not-to-use guidance.

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