Skip to main content
Glama
jarahkon

hass-mcp-server

by jarahkon

ha_update_scene

Update an existing Home Assistant scene by providing its ID and new configuration to modify its entities and states.

Instructions

Update an existing scene's configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_idYesThe scene ID to update
configYesUpdated scene config (same format as create)
Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits beyond the basic operation. Lacks information on side effects, error handling, or requirements (e.g., scene must exist).

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?

Single sentence, no superfluous words. Concise but at the expense of completeness.

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

Completeness3/5

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

Given the simplicity of the tool and full schema coverage, the description is moderately complete. However, it could include notes on error conditions or result behavior, especially lacking output schema.

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 has 100% description coverage for both parameters, so the tool description adds minimal additional meaning. The schema descriptions are adequate.

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?

Description clearly states the action (update) and resource (scene configuration). It distinguishes from sibling tools like create_scene and delete_scene, but could be more specific about the scope of 'configuration'.

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?

No guidance on when to use this tool vs alternatives such as ha_create_scene or ha_delete_scene. No explicit context for prerequisites or scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarahkon/hass-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server