bl-halo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| halo_deviceC | Halo / Frame glasses controller (portmanteau). Return Format
Examples
|
| halo_dashboardA | Halo status dashboard (Prefab App). Return Format
Examples
|
| halo_helpB | Halo help - operations, BLE pairing, Lua, Noa. Return Format
Examples
|
| halo_shutdownA | Disconnect Halo (destructive-guarded). Return Format
Examples
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| halo_recipe |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| halo_skill | |
| Prefab Renderer (halo_dashboard) |
TDQS
Scored across 4 tools
halo_device is a catch-all that overlaps with halo_dashboard (status vs. full dashboard) and can perform many actions, making its boundary fuzzy. halo_help and halo_shutdown are distinct, but the general-purpose nature of halo_device creates ambiguity.
All tools share the consistent halo_ prefix and use snake_case, creating a recognizable family. However, the second part mixes nouns (device, dashboard) with verbs (shutdown) and a noun/verb (help), which is a minor inconsistency.
Four tools is a well-scoped set for a niche device controller, avoiding both bloat and thinness. Each tool has a clear role, even if halo_device is broad.
Core operations like status, display text, photo capture, help, shutdown, and dashboard are covered. Missing explicit connect/pair or settings tools, but help references BLE pairing and the surface feels adequate for typical use.