mcp-airq

Official

Overview Schema Source Related Servers Discussions Admin

set_brightness

Idempotent

Control LED brightness of air-Q air quality sensors. Specify default brightness (0–100%) and optional night brightness for dimmed nighttime operation.

Instructions

Set LED brightness. 'default' is the normal brightness (0-100%), 'night' is optional night brightness.

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": {
      "default": "<default>"
    },
    "name": "set_brightness"
  }
}

Input Schema

Name	Required	Description	Default
`default`	Yes
`night`	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

A3.7/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds parameter context (default range, optional night) but does not disclose additional behavioral traits like side effects or permissions.

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?

The description is extremely concise at two sentences, front-loaded with the core action. Every sentence adds value without redundancy.

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?

The tool is simple with 3 parameters and an output schema. However, the description omits explanation for the 'device' parameter and does not discuss value bounds or error cases, leaving some gaps for complete understanding.

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?

With 0% schema coverage, the description partially compensates by explaining 'default' (0-100%) and 'night' (optional night brightness) but ignores the 'device' parameter. This leaves ambiguity for the device field.

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 'Set LED brightness' with a specific verb and resource. It distinguishes from sibling tools like get_brightness_config by indicating a write operation. The mention of 'default' and 'night' aligns with input parameters.

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?

The description implies use for setting brightness but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or prerequisites, which is adequate for a simple setter but lacks clarity on context.

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