Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Update a todo list item

todo_update_item
Destructive

Update a todo item's text or status in Home Assistant. Rename items or mark them needs_action/completed without affecting other fields.

Instructions

Update a todo item's text and/or status via the todo.update_item service.

Maps item to the service's rename field. Only the fields you pass (item/status) are sent, so whichever value is omitted is left unchanged on HA's side.

Use when: renaming an item or marking it needs_action/completed. Not for: adding a new item — use todo_add_item; not for removing one — use todo_remove_item. Returns: {"entity_id", "uid", "result": ...} where result is the service-call response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesItem UID to update, as returned by `todo_list_items`.
itemNoNew item text. Omit to keep the current text.
statusNoNew status: 'needs_action' or 'completed'. Omit to keep the current status.
entity_idYesTodo list entity ID the item belongs to, e.g. 'todo.shopping_list'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.25.1
    • addedInput schema / properties / entity_id / description
      Added value: +"Todo list entity ID the item belongs to, e.g. 'todo.shopping_list'."
    • addedInput schema / properties / item / description
      Added value: +"New item text. Omit to keep the current text."
    • addedInput schema / properties / status / description
      Added value: +"New status: 'needs_action' or 'completed'. Omit to keep the current status."
    • addedInput schema / properties / uid / description
      Added value: +"Item UID to update, as returned by `todo_list_items`."
  2. First observedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, non-idempotent, non-read-only, so the safety profile is carried structurally. The description adds genuinely useful behavior beyond that: partial-update semantics ('Only the fields you pass are sent, so whichever value is omitted is left unchanged'), which directly clarifies the non-idempotent hint.

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?

Front-loaded with the core action, then a mapping note, then explicit Use when / Not for / Returns lines. Every sentence carries information; no filler.

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?

With an output schema present, the description still summarizes the return shape, and it covers partial-update semantics, sibling routing, and the field mapping. Nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds information the schema does not carry: the `item` parameter maps to the service's `rename` field, and it restates the omit-to-keep behavior for both optional fields. That is real value beyond the schema text.

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 and resource ('Update a todo item's text and/or status') and even names the underlying service call. The mapping of `item` to the service's `rename` field tells the agent exactly what the operation does semantically.

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?

Explicit 'Use when' clause (renaming, marking needs_action/completed) and an explicit 'Not for' clause naming the two alternatives, `todo_add_item` and `todo_remove_item`. Routing is unambiguous.

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