Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

Switch the lamp to a session state

set_state
Idempotent

Switches host LEDs to a defined AI session state—idle, thinking, working, waiting, done, error, or off—so OpenRGB lighting shows the current conversation status.

Instructions

Switch the host LEDs to a conversation state.

state: idle | thinking | working | waiting | done | error | off (aliases such as complete/failed/ask are accepted). All animations are slow, continuous fades - the lamp never strobes. thinking = blue breathing, working = cyan breathing, waiting = amber fade, done = solid green, error = red fade, idle = dim blue breathing, off = lights out. detail is a short note kept in the status output. animate: set to false to freeze the effect.

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": {
      "state": "<state>"
    },
    "name": "set_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
detailNo
animateNo

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

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses real behavioral traits: every animation is a slow continuous fade, the lamp never strobes, and each state maps to a specific visual effect. It also reveals that 'detail' is persisted into the status output, which is not obvious from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then a compact per-state mapping. Slight redundancy between the state enumeration and the per-state color mapping, but each line carries distinct information an agent would otherwise have to guess.

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?

With an output schema present and annotations covering the safety profile, the description supplies what remains: valid inputs, aliases, visual semantics, and the detail note's destination. It does not address error behavior or how it composes with the other state/effect tools, which is the only remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: it lists all seven state values plus accepted aliases, explains that 'detail' is a short note kept in the status output, and clarifies that 'animate=false' freezes the effect. All three parameters gain meaning not present in the bare schema.

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?

States a specific verb and resource: 'Switch the host LEDs to a conversation state', and immediately enumerates the accepted state values. It is clear what the tool does, though it never names when to prefer it over siblings like set_color, set_effect, or set_progress.

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?

Usage is implied rather than stated: an agent infers it should call this to signal session status (thinking/working/done/error). There is no explicit when-to-use, when-not-to-use, or comparison against the closely related siblings set_color, set_effect, and set_progress.

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