Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

Set a single colour on all LEDs

set_color
Idempotent

Paints every OpenRGB LED a single #RRGGBB color with optional brightness scaling from 0 to 1 to create uniform status lighting.

Instructions

Paint every LED with one colour (#RRGGBB). brightness (0-1) scales it.

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": {
      "color": "<color>"
    },
    "name": "set_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
brightnessNo

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

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

Annotations already disclose write, idempotent, and non-destructive behavior, so the bar is lower. The description adds the useful detail that brightness multiplies the colour, but it does not say whether this replaces a running effect or progress display, or whether the setting persists across reconnects.

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, zero filler, and the operation and its scope are front-loaded before the optional modifier. Every clause conveys information an agent needs.

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 two-parameter fill tool with an output schema and full annotation coverage, the definition covers the essentials: scope, colour format, and brightness scaling. The only material gap is interaction with currently running effects or progress state.

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?

With 0% schema description coverage, the description carries the full burden and mostly meets it: it fixes the colour format as #RRGGBB and gives brightness a concrete 0-1 range plus its effect ("scales it"). It leaves the null default of brightness unexplained, so the reader cannot tell whether null means full brightness or the current level.

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?

"Paint every LED with one colour" gives a concrete verb (paint), an explicit scope (every LED), and the target resource, which implicitly separates it from the per-LED sibling set_leds. It stops short of naming an alternative, so the differentiation is inferred rather than stated.

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 word "every" implies this is the uniform-fill option and that set_leds would be used for per-LED control, but the description never states when to pick this over set_effect, set_progress, set_state, or restore. Usage is only implied by scope wording, with no exclusions or preconditions.

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