mcp-airq

Official

by CorantGmbH

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_possible_led_themes

Read-only

Get a list of all LED themes supported by your air-Q sensor. Use this to select a theme for the device's LED display.

Instructions

List all available LED visualization themes for 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_possible_led_themes"
  }
}

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

A3.5/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the description's 'list' action is consistent. However, the description does not add behavioral context beyond what annotations already provide, such as whether the device must be connected or the response format. It is adequate but not enhanced.

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 sentence that is front-loaded and concise. Every word is necessary—no fluff or redundancy.

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?

Given the tool's simplicity (one optional parameter, read-only, output schema exists), the description covers the primary purpose. However, it could be improved by noting the parameter's optionality and default behavior, but this is partly in the schema. Still, it is mostly complete for the task.

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?

The input schema has 1 parameter ('device') with 0% description coverage. The description does not explain the parameter's meaning, usage, or default behavior. Despite the parameter being optional, the absence of any elaboration fails to compensate for the low schema coverage.

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 that the tool 'list all available LED visualization themes for a device.' It uses a specific verb ('list') and resource ('available LED visualization themes'), distinguishing it from siblings like 'get_led_theme' (current theme) and 'set_led_theme' (set 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 viewing available themes, but does not explicitly state when to use it versus alternatives (e.g., 'get_led_theme' for current theme) or provide context for when not to use it. The purpose is clear but lacks direct guidance.

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