mcp-airq

Official

Overview Schema Source Related Servers Discussions Admin

get_config

Read-only

Retrieve the full configuration of an air quality sensor as a JSON dictionary, including a _config_guide field with documentation for all keys.

Instructions

Get the full configuration of a device as a JSON dict.

The response includes a _config_guide field with full documentation of
all configuration keys — read it before interpreting or modifying values.

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

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.8/5.0

Behavior4/5

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

Annotations indicate a safe read operation. The description adds behavioral context by noting the response includes a _config_guide field for interpreting keys, which advises a recommended workflow for agents. No contradiction with 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?

Two sentences, front-loaded with the core purpose. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (1 optional param, read-only, output schema present), the description provides sufficient context about what it returns and how to interpret results. It covers the essential aspects for correct usage.

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

Parameters2/5

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

The single parameter 'device' has 0% schema description coverage, yet the description does not explain its meaning, default behavior, or effect when omitted. This leaves a significant gap for the agent.

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 tool retrieves the full configuration of a device as a JSON dict. This verb+resource combination is specific and distinguishes it from siblings that deal with individual settings or operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies a read-only context but omits scenarios or exclusions, such as when to use get_device_info instead.

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