Skip to main content
Glama
Vortitron

home-assistant-mcp

by Vortitron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get error log

ha_get_error_log
Read-only

Retrieve the tail of raw Home Assistant error logs when you need original line ordering or entries omitted by structured system log views.

Instructions

Return the tail of the raw Home Assistant error log. ha_get_system_log is usually the better first stop (grouped and structured); reach for this one when you need the raw ordering, or lines the structured store drops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tail_linesNoNumber of trailing lines to return (default 200).
instance_idNoOptional: the instance you mean (as listed by vomehome_list_instances). When given, the call is refused if this session is targeting a different home, instead of answering from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: this is the raw, ungrouped log and the structured store may drop lines, which explains why the two tools can disagree. It doesn't mention the default tail size or the foreign-instance refusal, but those live in the schema.

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?

Two sentences with no filler, and the primary routing decision is front-loaded immediately after the one-line purpose statement.

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?

For a two-parameter read-only log tool with full schema coverage and no output schema, the description supplies enough to call it correctly and to pick it over the structured-log sibling. Only the return shape/pagination is unaddressed, which is minor here.

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% for both parameters, including the default of 200 lines and the instance_id refusal semantics, so the schema carries the load. The description adds no parameter-level detail beyond what is already documented.

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 ('Return the tail of the raw Home Assistant error log') and contrasts it with the sibling ha_get_system_log, so an agent can distinguish the two logs 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?

Explicit routing guidance: ha_get_system_log is named as the usual better first stop, and the exact conditions for choosing this tool instead (raw ordering, lines the structured store drops) are spelled out.

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