Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set entity value

entities_set_value
Idempotent

Set numeric values on input_number, number, or climate entities in Home Assistant, dispatching to the correct service per domain.

Instructions

Set the numeric value of an input_number, number or climate entity.

Dispatches to input_number.set_value, number.set_value or climate.set_temperature depending on entity_id's domain; any other domain raises ValueError before any HTTP call is made.

Use when: writing a target number or temperature to one of these three domains. Not for: input_text, input_select, input_boolean or input_datetime — use helpers_set_input_text, helpers_set_input_select, helpers_set_input_boolean or helpers_set_input_datetime. Returns: the list of changed states from Home Assistant. Errors: raises ValueError for any domain other than input_number, number or climate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesNumeric value to write; interpreted per domain, see Behaviour.
entity_idYesFull entity ID to set, e.g. 'input_number.target_temp'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.25.1
    • addedInput schema / properties / entity_id / description
      Added value: +"Full entity ID to set, e.g. 'input_number.target_temp'."
    • addedInput schema / properties / value / description
      Added value: +"Numeric value to write; interpreted per domain, see Behaviour."
  2. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare safety traits, and the description goes further by explaining domain-based dispatch, pre-HTTP ValueError behavior for unsupported domains, and return of changed states.

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?

Purpose is front-loaded, then structured sections for usage, returns, and errors. Every sentence is useful, with no filler; the returns and errors notes remain helpful even though an output schema exists.

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 moderate complexity, full schema coverage, annotations, and an output schema, the description is complete: it covers routing, valid domains, error handling, and expected output.

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 description coverage is 100%, so both parameters are already documented. The description adds only that value is interpreted per domain and that entity_id's domain selects the underlying service, which is minimal additional parameter-level detail.

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?

States a specific verb ('Set'), resource ('numeric value'), and the exact three entity domains it supports. It distinguishes itself from non-numeric helper tools by naming them and pointing to their alternatives.

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

Usage Guidelines5/5

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

Explicitly provides 'Use when' guidance for writing numeric values or temperatures, and 'Not for' exclusions for input_text, input_select, input_boolean, and input_datetime with the correct sibling alternatives named.

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