Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

Set per-LED colours

set_leds
Idempotent

Set an individual color for every LED on an OpenRGB device by supplying one #RRGGBB value per LED; use it to render gradients, patterns, progress bars, or remaining-quota indicators.

Instructions

Set an explicit colour per LED (#RRGGBB). The list length must equal the device's LED count - query it with list_devices. Use it for gradients and patterns.

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": {
      "colors": "<colors>"
    },
    "name": "set_leds"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYes

Output Schema

NameRequiredDescriptionDefault
fpsYes
portYes
quotaNo(remaining, total)
ratioNo
stateYes
totalNo
zonesNo
agentsNoall agents currently sharing the lamp
detailYes
deviceYes
animateYes
controlNo'global' = the whole strip is controlled as one unit, 'per_led' = every LED is written individuallyglobal
percentNo
agent_idNoid of this agent in the shared registry
progressNo0..1
restoredNo
led_countYes
remainingNo
brightnessYes
last_errorYes
active_modeYes
filled_ledsNo
render_modeNo'hardware' = the controller animates on its own, 'per_led' = colours are written LED by LEDper_led
state_age_sYes
custom_colorYes
display_stateNostate currently shown on the lamp (highest priority of all agents)idle
protocol_versionYes
animation_runningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare writable but idempotent and non-destructive, so the safety profile is covered. The description adds the real behavioural constraint an agent would otherwise trip over: the array length must match the device LED count, discoverable via list_devices. That is useful context beyond annotations, though error behaviour and effect on any prior state are still unstated.

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?

Two sentences, front-loaded with the action and value format, then the hard constraint, then the use case. Every clause earns its place with no repetition of the title or schema.

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

Completeness4/5

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

For a one-parameter tool with an output schema and usable annotations, the description covers action, format, constraint, and prerequisite. Only edge-case behaviour (invalid hex, length mismatch failure mode) is absent, which is a minor gap at this complexity.

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 0% (the single parameter is a bare array of strings), so the description carries the burden and largely discharges it: it fixes the colour syntax as #RRGGBB and the hard length constraint (must equal the device's LED count). It does not say what happens on a length mismatch, but the essential semantics are added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set an explicit colour per LED (#RRGGBB)" gives a specific verb, resource, and value format, and the per-LED framing implicitly separates it from the single-colour sibling set_color. It stops short of naming an alternative explicitly, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a positive use case ("gradients and patterns") and a prerequisite workflow ("query it with list_devices" for the LED count). There is no explicit when-not guidance or named alternative, so the routing side is only partially covered.

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