BLE MCP Server

by es617

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

ble_plugin_load

Load a Bluetooth Low Energy plugin from a .py file or directory to extend server capabilities.

Instructions

Load a new plugin from a file or directory path. Requires BLE_MCP_PLUGINS env var to be set.

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": {
      "path": "<path>"
    },
    "name": "ble_plugin_load"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to a .py file or directory containing __init__.py.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only mentions an environment variable requirement, but does not disclose side effects, return behavior, or what happens after loading (e.g., immediate activation, error handling).

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 consists of two concise, well-structured sentences with no unnecessary words. It front-loads the core action and adds a key requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite clear purpose, the description lacks details on return values, success/failure indicators, and potential side effects. Since there is no output schema, the description should compensate, but it does not.

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%, and the description adds meaningful context beyond the schema by specifying the environment variable prerequisite. The description adds value without redundancy.

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 action ('Load a new plugin') and the resource ('from a file or directory path'), and distinguishes it from sibling plugin tools like 'ble_plugin_list' and 'ble_plugin_reload'.

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 mentions a prerequisite (BLE_MCP_PLUGINS env var) but does not provide guidance on when to use this tool compared to alternatives like 'ble_plugin_reload' or 'ble_plugin_template'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.