Skip to main content
Glama

flipper_led

Idempotent

Set the Flipper Zero RGB status LED by specifying red, green, and blue channel values from 0 to 255, letting agents signal device state visually.

Instructions

Set the RGB status LED (each channel 0-255).

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": {
      "r": "<r>",
      "g": "<g>",
      "b": "<b>"
    },
    "name": "flipper_led"
  }
}

Input Schema

NameRequiredDescriptionDefault
bYes
gYes
rYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnly=false, idempotent=true, destructive=false, so safety behavior is covered. The description contributes the channel range (0-255), but says nothing about whether the LED persists after the call, whether it overrides an existing LED state, or whether a reset is needed — useful gaps for a state-setting tool. With annotation coverage, this earns a middle score.

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?

A single short sentence with the resource and the value constraint front-loaded. Nothing redundant and nothing 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?

An output schema exists, so return values need not be explained, and three required integer parameters are simple to call. The only real omission is post-call LED behavior (persistence, override, reset), which is minor for a three-parameter setter.

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

Parameters3/5

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

Schema description coverage is 0% and the properties carry only bare titles "R", "G", "B", so the description must compensate. It does partially by establishing the values are channels with a 0-255 range and by implying standard RGB ordering, but it never explicitly maps each parameter to its channel or states what out-of-range values do.

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?

Specific verb plus resource: "Set the RGB status LED" tells an agent exactly what changes and what entity it touches. It does not name a sibling or explicitly distinguish itself from tools like flipper_vibro, but the purpose is unambiguous without opening the schema.

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

Usage Guidelines2/5

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

The description gives no when-to-use context, no prerequisites, and no mention of when not to call it (e.g. versus other notification tools). The agent must infer everything about invocation conditions from the tool name alone.

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