Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

List OpenRGB devices

list_devices
Read-only

Read the OpenRGB device inventory—devices, zones, modes, and LED counts—to discover each device's LED total and size progress bars correctly.

Instructions

Read the OpenRGB device inventory: devices, zones, modes and how many LEDs each device has. The LED count is the length of a progress bar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
portYes
devicesYes
selectedYes
led_countYestotal LEDs of the selected device (progress bar length)
protocol_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description only needs to add substance, which it does by disclosing that the response spans multiple entity types (devices, zones, modes) and by defining the LED count semantics. It stops short of noting freshness, ordering, or whether the inventory reflects a live scan.

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 resource, then the one non-obvious semantic detail. Nothing is redundant or padded.

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 zero parameters, the description need not document return shapes, and it does not. For a simple read-only enumeration it is nearly complete; a note on whether results are cached or require a device rescan would close the remaining gap.

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?

The tool takes no parameters, so the schema has nothing to document and the baseline of 4 applies. The description correctly spends no words on arguments and instead explains the meaning of a returned value.

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?

The description opens with a specific verb and resource, "Read the OpenRGB device inventory," and enumerates what the inventory contains (devices, zones, modes, LED counts). That makes the tool's job unmistakable and implicitly separates it from the set_* mutators, though no sibling is named explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance. The single hint, "The LED count is the length of a progress bar," implies this tool supplies the sizing input for progress-related calls such as set_progress, but the agent must infer that connection rather than being told to call this first.

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