mcp-airq

Official

Overview Schema Source Related Servers Discussions Admin

set_led_theme

Idempotent

Change the LED theme on your air-Q sensor to visualize specific air quality parameters like CO2, VOC, or PM2.5. Select a theme for the left, right, or both sides of the device.

Instructions

Set the LED visualization theme for one or both sides of the device.

Common themes: 'standard', 'CO2', 'VOC', 'Humidity', 'PM2.5', 'Noise'.
Use get_possible_led_themes to see all available themes.

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_theme"
  }
}

Input Schema

Name	Required	Description	Default
`left`	No
`right`	No
`device`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.3Jun 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true, so the description adds value by listing common theme values and noting that themes are named. It aligns with annotations (readOnlyHint=false, destructiveHint=false) and does not contradict them.

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 concise sentences with no redundant information. The first sentence states purpose, the second adds helpful examples and a pointer to another tool. Every sentence earns its place.

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?

Covers the main purpose and provides theme examples. Output schema exists, so return values need not be described. However, it does not clarify behavior when both parameters are null or the effect of setting only one side. Still, it is mostly complete for a simple 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 parameter descriptions are absent (0% coverage). The description partially compensates by mentioning 'one or both sides' and listing example theme names, but does not explicitly describe each parameter (left, right, device) or their allowed values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'set' and the resource 'LED visualization theme', specifying the scope 'for one or both sides of the device'. It effectively distinguishes from sibling tools like get_led_theme (get vs set) and other set tools.

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?

Provides explicit examples of common themes and directs users to get_possible_led_themes for a complete list. This gives clear context on how to use the tool, though it does not explicitly state when not to use it.

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