Retrieve all Home Assistant entity states for monitoring, analysis, and troubleshooting of your smart home.
List Home Assistant entity states (can be large).
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ha_list_states"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds the useful warning that the response 'can be large', which is a behavioral trait. However, it does not clarify what a 'state' includes (e.g., full state objects, attributes, last_updated), nor does it mention potential pagination or rate limits. The size warning is a moderate disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single concise sentence that front-loads the core purpose and adds a meaningful caveat. Every word earns its place; no fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple nature of the tool (no parameters) and the presence of sibling tools that provide differentiation, the description is largely adequate. It states what the tool does and a key behavioral constraint. It could mention what the return value looks like, but the output schema is absent and not strictly required for such a straightforward list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the schema coverage is 100% (empty object). The baseline for no parameters is 4, and the description need not elaborate on parameter semantics since none exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' and identifies the resource as 'Home Assistant entity states', which clearly distinguishes this from sibling tools like ha_get_state (which retrieves a single state) and ha_list_services or ha_list_areas (which list other kinds of entities).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is provided about when to use this tool versus alternatives. The parenthetical '(can be large)' implies a cautionary note, but it does not suggest using ha_get_state for individual states or mention any exclusions. The description relies solely on the tool's name for context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.