Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

Show remaining budget as an LED bar

set_quota
Idempotent

Display remaining budget on an LED strip, filling the bar proportionally and coloring it green, amber, or red based on quota left. Use for tokens, API balance, or steps.

Instructions

Show how much of a budget is left using the LED count: the bar is filled proportionally to remaining/total and coloured green above 50%, amber between 20% and 50%, red at 20% or less.

Use it for token budgets, API balance, remaining steps and similar.

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": {
      "remaining": "<remaining>",
      "total": "<total>"
    },
    "name": "set_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
totalYes
detailNo
remainingYes

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

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail the annotations cannot express: proportional fill and the green/amber/red thresholds at 50% and 20%. It does not say whether a prior bar is overwritten or what the 'detail' parameter renders.

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?

Two short sentences, front-loaded with the rendering rule and thresholds before the usage sentence. No filler; only a stray line break interrupts the flow.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the visual behavior is well covered. However, with three parameters at 0% schema coverage and 'detail' undocumented, an agent still lacks enough to call it confidently in all cases.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it only partially does: it implies the remaining/total ratio drives the fill but never describes units, ranges, or clamping behavior. The optional 'detail' parameter is entirely unexplained in both schema and description.

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 action (render a proportional LED bar showing remaining/total) plus the exact color thresholds, which is far more concrete than the title alone. It is distinguishable from generic siblings like set_leds or set_state, though it never names how it differs from the very similar set_progress sibling.

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?

The second sentence gives concrete usage contexts (token budgets, API balance, remaining steps), which tells an agent when this is the appropriate tool. It stops short of explicit exclusions or naming an alternative such as set_progress, so it is clear context without disambiguation.

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