HomeLab MCP

by chip10

Overview Schema Source Related Servers Discussions Admin

Python

Local

ha_error_log

Retrieve the Home Assistant session error log to diagnose problems and resolve failures.

Instructions

Obtiene el error_log de la sesión actual.

Tool call template

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_error_log"
  }
}

Input Schema

Name	Required	Description	Default
`max_characters`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states that the tool obtains the current session's error log, but does not describe output characteristics, filtering behavior, size limitations, or whether this is a read-only diagnostic operation.

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?

The description is a single concise sentence with no fluff or redundant wording. It front-loads the core purpose, though it is so brief that it does not provide additional structural context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has only one optional parameter, and has an output schema, so minimal description may be acceptable. However, given the lack of annotations and the absence of parameter semantics, the description does not fully enable an agent to understand the tool's behavior or make informed decisions about the max_characters argument.

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

Parameters1/5

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

The schema describes one parameter, max_characters, with 0% description coverage. The description does not mention or explain this parameter, its purpose, or how it affects the returned error log. The default value is visible in the schema, but the description adds no semantic value.

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?

The description states a specific verb ('Obtiene') and a specific resource ('el error_log de la sesión actual'), clearly identifying what the tool does. It is distinct from sibling tools, which focus on guests, entities, services, containers, and other resources rather than session error logs.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives. It does not mention related tools, exclusions, or conditions that would make this the appropriate choice over logs from docker_container_logs or health checks like ha_check.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.