Skip to main content
Glama
Sign In
ha-automation-mcp

ha-automation-mcp

by aderik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_dashboard_config

Overwrite a Home Assistant Lovelace dashboard's full configuration by providing url_path and a config object containing views.

Instructions

Overwrite the entire Lovelace config of a dashboard.

config must contain at least {"views": [...]}.

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": {
      "url_path": "<url_path>",
      "config": "<config>"
    },
    "name": "set_dashboard_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYes
url_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the destructive scope ('overwrite the entire') and a minimum-content constraint, which is useful. However, it says nothing about irreversibility, permissions, or what happens to existing keys not supplied, leaving the mutation risk under-described.

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 short sentences, zero filler, and the destructive scope is front-loaded before the format constraint. Nothing to trim.

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?

For a nested-object mutation tool with no annotations and no output schema, it covers the essential risk (full overwrite) and the config shape requirement. The gap is `url_path` semantics and the fate of omitted top-level keys, but overall it is adequately complete.

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?

Schema coverage is 0%, so the description must compensate. It adds real meaning for `config` by requiring at least `{"views": [...]}`, but `url_path` (which dashboard to target) is left entirely undefined despite being required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: overwrite the entire Lovelace config of a dashboard. The word 'entire' implicitly distinguishes it from partial siblings like replace_dashboard_view or append_dashboard_card, though no sibling is named explicitly.

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?

Usage is implied rather than stated: a full overwrite is the right call when you want to replace the whole config, versus the view/card-level siblings. There is no explicit 'use this when / use X instead' guidance, so the agent must infer the routing from the word 'entire'.

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

Deploy Server

Other Tools