qidi-mcp

set_led

Idempotent

Set an RGB(W) LED strip's color on a QIDI Max 4 printer with 0.0–1.0 red, green, blue, and white values; omit the index to update the whole LED chain.

Instructions

Set an RGB(W) LED strip's colour. Components are 0.0–1.0. On the Max4 the strip is 'RGB' (25 LEDs); omit index to set the whole chain.

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": "set_led"
  }
}

Input Schema

Name	Required	Description	Default
`led`	No
`red`	No
`blue`	No
`green`	No
`index`	No
`white`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds a real side-effect disclosure, that omitting index writes all 25 LEDs at once, and states the valid component range 0.0-1.0. It does not cover failure modes or what happens for a strip that does not support White.

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?

Three short sentences pack the value range, the device-specific strip name, and the whole-chain rule together, with the core action stated first. Nothing is padded or repeated from the schema.

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 tool itself is simple. Even so, the defaults (red, green, blue, and white all 0; led and index null) mean a bare call sets black on all LEDs, and the description does not clarify index numbering or behavior on multi-strip setups. These are real gaps for a 6-parameter, 0%-described schema.

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%, so the description must compensate. It does explain the 0.0-1.0 component range, that index may be omitted, and that led='RGB' on the Max4. It leaves the index being 0-based or 1-based, whether the led parameter is required, and whether white applies only to RGBW strips undocumented.

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 states a specific verb and resource: 'Set an RGB(W) LED strip's colour'. It also gives concrete device context ('On the Max4 the strip is RGB, 25 LEDs'). However, it never explicitly distinguishes this from the sibling tool set_case_light, so the agent must infer the difference from the resource name alone.

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?

It gives one concrete usage rule: omit index to set the whole chain. That is implied guidance for addressing the whole strip vs a single LED. It says nothing about when to pick this over set_case_light, and nothing about prerequisites such as the led strip being present or configured.

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

Deploy Server