Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add a todo list item

todo_add_item

Add a new item to a Home Assistant todo list with optional due date and notes; use for new entries only, not updates.

Instructions

Add a new item to a todo list via the todo.add_item service.

Sends due_date or due_datetime depending on whether due_date contains a time component ('T' or a space). Calling this twice with the same item text creates two separate items with distinct uids.

Use when: adding a new entry to a todo list. Not for: changing or completing an existing item — use todo_update_item. Returns: {"entity_id", "item", "result": ...} where result is the service-call response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYesItem text, e.g. 'Buy milk'.
due_dateNoOptional due date ('YYYY-MM-DD') or datetime ISO string. Omit for no due date.
entity_idYesTodo list entity ID to add the item to, e.g. 'todo.shopping_list'.
descriptionNoOptional longer item description/notes. Omit for none.

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 / description / description
      Added value: +"Optional longer item description/notes. Omit for none."
    • addedInput schema / properties / due_date / description
      Added value: +"Optional due date ('YYYY-MM-DD') or datetime ISO string. Omit for no due date."
    • addedInput schema / properties / entity_id / description
      Added value: +"Todo list entity ID to add the item to, e.g. 'todo.shopping_list'."
    • addedInput schema / properties / item / description
      Added value: +"Item text, e.g. 'Buy milk'."
  2. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing the duplicate-creation semantics (calling twice creates two items with distinct uids) and the due_date vs due_datetime dispatch logic, which are non-obvious behaviors an agent must anticipate. It is somewhat redundant in restating the return shape despite an output schema existing.

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?

Front-loaded with the core action, then behavior, usage, exclusion, and return value in a tight structured layout. The 'Returns' block is partly redundant given the output schema, which is a minor waste but does not undermine clarity.

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 a 4-parameter tool with full schema coverage, annotations, and an output schema, the description covers intent, usage, alternatives, duplicate semantics, and date handling. The only nit is duplicated return-value detail, but nothing an agent needs to call it correctly is missing.

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 all four parameters are already documented in the schema; the baseline is 3. The description adds the date-vs-datetime dispatch rule, which is useful, but the other three parameters receive no additional description-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 (add) and resource (todo list item) and names the underlying `todo.add_item` service. It explicitly distinguishes itself from `todo_update_item`, so an agent can tell it apart from its nearest sibling without opening either schema.

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?

Provides an explicit 'Use when' and 'Not for' pair, naming the alternative tool (`todo_update_item`) and the condition that selects it. Nothing about tool selection is left to inference.

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