Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get audit log

get_audit_log
Read-onlyIdempotent

Review recent Home Assistant tool calls that can change the system, including previews, rejections, execution status, and sanitized arguments.

Instructions

Recent calls to tools that can change Home Assistant, newest first, including previews and rejections. Each entry records the tool, status, whether anything was executed and the arguments (credentials removed).

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": "get_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoOnly entries for this tool.
limitNoHow many entries to return.
executed_onlyNoOnly calls that actually changed something.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: ordering (newest first), inclusion of previews and rejected calls, and redaction of credentials. Return shape is described at field level, which matters since no output schema exists.

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?

Two sentences, both front-loaded with the most decision-relevant information (what is logged, ordering) before the entry contents. Tight and free of filler, though the second sentence is a fairly dense list.

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?

With no output schema, the description needs to convey what an entry contains, and it does (tool, status, executed flag, redacted arguments). For a simple three-parameter read tool this is nearly complete, with only the relationship to sibling log tools left unstated.

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 coverage is 100%, so all three parameters are already documented, establishing a baseline of 3. The description adds only marginal meaning by saying entries record 'whether anything was executed', which loosely glosses executed_only, but adds nothing for tool or limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (audit log of tool calls) and narrows the scope precisely to 'calls to tools that can change Home Assistant', which separates it from state-oriented logs like get_logbook or get_system_log. It does not name a sibling explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for auditing mutating tool calls, but the description never says when to prefer it over get_logbook, get_system_log, or explain_state_change. No exclusions or prerequisites are stated.

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