openwebnet-mcp

Overview Schema Source Related Servers Score Discussions Admin

Draft Ha Config

draft_ha_config

Generate production-ready Home Assistant YAML configuration for any MyHOME entity by specifying platform, name, and OpenWebNet address.

Instructions

Generate production-ready Home Assistant YAML configuration for any MyHOME entity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mac`	No	Physical gateway MAC address (mandatory in modern MyHOME integration).	00:03:50:xx:xx:xx
`who`	No	Subsystem WHO code for binary sensors (default '25' for dry contacts, '1' for motion, '9' for aux) (platform=binary_sensor).	25
`name`	Yes	Friendly name for the entity (e.g. 'Living Room Dimmer', 'Garage Door Contact').
`where`	Yes	OpenWebNet bus address (e.g. '12', '21#4#1', '31').
`dimmable`	No	True if light is dimmable (platform=light).
`platform`	Yes	Platform type ('light', 'cover', 'climate', 'sensor', 'binary_sensor', 'switch', 'media_player').
`run_time`	No	Full travel runtime in seconds (platform=cover).
`gateway_id`	No	Gateway identifier for /config/myhome.yaml (e.g. 'f454', 'mh202').	f454
`transition`	No	Default transition speed 1-10 (platform=light).
`sensor_type`	No	Type of sensor measurement ('power', 'energy', 'temperature') (platform=sensor).	power
`cool_support`	No	Enable cooling capability (platform=climate).
`device_class`	No	Binary sensor device class ('opening', 'motion', 'garage_door', 'door', 'window') (platform=binary_sensor).	opening
`heat_support`	No	Enable heating capability (platform=climate).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A3.5/5.0

Behavior2/5

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

The description is minimal and does not disclose any behavioral traits beyond what the schema provides. With no annotations provided, the description carries the full burden. It doesn't mention whether the generation is one-shot, whether it validates inputs, what happens if the platform doesn't match parameters (e.g., providing 'dimmable' with platform=cover - probably ignored), or whether it overrides existing configs. The schema has rich default values and parameter descriptions, but the overall behavior of the tool (e.g., whether it returns errors on invalid combinations) is not disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and to the point. It front-loads the purpose with 'Generate' and specifies the output type. It doesn't waste any words. However, it could expand slightly on usage without becoming bloated, but for a tool description that relies on schema, this is efficient.

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 complexity (13 parameters, 7 platform types) and the rich schema with per-parameter descriptions and defaults, the description is adequate for an agent to understand the tool's scope. The output schema likely details the generated YAML structure, so the description doesn't need to explain return values. The main gap is usage guidance, but with the schema's parameter descriptions, an agent can infer how to use it.

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?

The schema description coverage is 100%, meaning each parameter has a description in the schema. The tool description adds no additional meaning beyond the schema. For example, the description doesn't explain the relationship between 'who' and 'platform' beyond what's in the schema. Given the high coverage, a baseline of 3 is appropriate; the description does not add extra semantic value.

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's purpose: 'Generate production-ready Home Assistant YAML configuration for any MyHOME entity.' It specifies the exact resource (Home Assistant YAML configuration) and the domain (MyHOME entities). It also suggests the output is ready-to-use, which is helpful for the agent. It doesn't explicitly name a sibling tool to differentiate from, but given the sibling list contains related tools like 'draft_own_frame' and 'get_ha_guide', the purpose is specific enough that an agent won't confuse it with the others.

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: when you need a Home Assistant YAML config for a MyHOME entity. It does not explicitly state when not to use it or mention alternative tools like 'lookup_frame_syntax' or 'get_ha_guide'. The context suggests it could be used alongside 'get_ha_guide' for guidance, but this is not explicitly stated. The tool is self-described as the way to generate configs, but no exclusions are given.

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

Install Server