pixelblaze
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIXELBLAZE_HOST | Yes | Your PixelBlaze IP address |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pixelblaze_list_patternsA | List all patterns stored on the PixelBlaze device. Returns a list of dicts with 'id' and 'name' keys. |
| pixelblaze_get_active_patternA | Get the currently active (running) pattern on the PixelBlaze. Returns a dict with 'id' and 'name' of the active pattern. |
| pixelblaze_set_active_patternA | Switch the PixelBlaze to run a specific pattern by its ID. Args: pattern_id: The pattern ID to activate (from pixelblaze_list_patterns). Returns a confirmation message. |
| pixelblaze_get_pattern_codeA | Get the JavaScript source code of a pattern. Args: pattern_id: The pattern ID to retrieve code for. Returns the JavaScript source code string. |
| pixelblaze_create_patternA | Create a new pattern on the PixelBlaze with the given JavaScript code, then activate it. Args: name: Display name for the new pattern. code: PixelBlaze JavaScript source code (must define a render(index) function). Returns a dict with the new pattern's 'id' and 'name'. |
| pixelblaze_update_patternA | Replace the JavaScript source code of an existing pattern. Args: pattern_id: The ID of the pattern to update. code: New PixelBlaze JavaScript source code. Returns a confirmation message. |
| pixelblaze_delete_patternC | Delete a pattern from the PixelBlaze device. Args: pattern_id: The ID of the pattern to delete. Returns a confirmation message. |
| pixelblaze_get_controlsA | Get the UI controls for the currently active pattern. Returns a list of control dicts, each with 'name', 'value', and 'type' keys. The controls correspond to exported slider/toggle/picker variables in the pattern code. |
| pixelblaze_set_controlA | Set the value of a UI control (slider, toggle, etc.) on the active pattern. Args: name: The control variable name (as it appears in pixelblaze_get_controls). value: Numeric value (sliders: 0.0–1.0; toggles: 0 or 1). Returns a confirmation message. |
| pixelblaze_get_device_infoA | Get hardware and runtime information about the PixelBlaze device. Returns a dict with keys: host, pixel_count, fps, uptime_s, version_major, version_minor. |
| pixelblaze_set_brightnessA | Set the global brightness of the PixelBlaze. Args: value: Brightness level from 0.0 (off) to 1.0 (full brightness). Returns a confirmation message. |
| docs_get_api_referenceA | Get the full PixelBlaze language reference (electromage.com/docs/language-reference). This covers all built-in functions available when writing pattern code: render(index), beforeRender(delta), color functions (hsv, rgb), math/waveform functions (time, wave, triangle, sin, cos, etc.), array functions, 2D/3D rendering, UI controls (sliders, pickers), language features and limitations, variables, constants, and more. Always call this before writing or editing any PixelBlaze pattern code. |
| docs_get_mapper_referenceA | Get the PixelBlaze 2D/3D pixel mapping reference documentation. This covers how to define spatial coordinates for pixels using the mapper, coordinate systems, and the render2D/render3D pattern functions. Call this when working with multi-dimensional LED layouts or spatial effects. |
| docs_fetch_pageA | Fetch the text content of a PixelBlaze documentation page from the web. Use this to look up specific pages on electromage.com/docs/ that aren't covered by the cached API reference, such as hardware-specific guides, GPIO, networking, or advanced topics. Args: url: Full URL of the documentation page (e.g. https://electromage.com/docs/GPIO/). Returns the page text content, or an error message if unreachable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| device_context | Current PixelBlaze device connection info. |
TDQS
Scored across 14 tools
Each tool targets a distinct action: documentation tools are separated by page type, and device tools cover unique operations (CRUD, controls, brightness, info) with no overlap.
All tools follow a consistent snake_case format with the server name prefix (docs_ or pixelblaze_) followed by a verb and noun, making the purpose clear.
14 tools is well-scoped for managing PixelBlaze patterns, controls, brightness, and documentation; neither too sparse nor overwhelming.
Covers full lifecycle of patterns (CRUD, activation), brightness, control manipulation, device info, and essential documentation references with no obvious gaps.