mcp-airq

Official

by CorantGmbH

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_led_theme

Read-only

Retrieve the current LED color theme for both sides of an air-Q air quality sensor device.

Instructions

Get the current LED visualization theme for both sides of a device.

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

Input Schema

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

B3.3/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds no additional behavioral context beyond what annotations provide, such as authentication requirements or side effects. It is consistent but does not add value beyond annotations.

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 a single, front-loaded sentence of 14 words with no redundancy. Every word contributes to understanding the tool's action and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description clearly states the tool's purpose and a potential output exists (output schema present), it lacks essential information about the sole parameter. Without parameter documentation, the description is incomplete for correct usage.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the 'device' parameter, its format, or its role. The agent has no guidance on how to specify the device, making the tool difficult to invoke correctly.

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 'Get', the resource 'current LED visualization theme', and the scope 'for both sides of a device.' It distinguishes itself from sibling tools like 'get_possible_led_themes' (lists all themes) and 'set_led_theme' (changes the theme).

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 usage for reading the current theme, but does not explicitly state when to use this tool versus alternatives like 'get_possible_led_themes' or 'set_led_theme'. No exclusions or prerequisites are mentioned.

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