Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get calendar events

get_calendar_events
Read-onlyIdempotent

List calendar entities or retrieve a specific calendar's events between two dates, defaulting to the next 7 days. Use it to check upcoming appointments and schedule availability.

Instructions

List calendar entities, or the events of one calendar between two times (default: the next 7 days).

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

Input Schema

NameRequiredDescriptionDefault
endNoISO end. Defaults to 7 days after start.
startNoISO start. Defaults to now.
entity_idNoCalendar entity such as calendar.family. Omit to list calendars.
max_itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the default window of the next 7 days — but says nothing about the 50-item default cap, the 500 maximum, or whether results are truncated silently.

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?

A single front-loaded sentence with no filler. The parenthetical default is compact, though folding a time-window default into the same clause as the two listing modes makes it marginally dense.

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 simple read-only list tool with four optional parameters, no output schema and full annotation coverage, the description covers both modes and the default range, which is most of what an agent needs. The remaining gap is result-set size behavior (default 50, max 500, truncation), which is the main thing an agent could get wrong 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 75%, so the schema already documents start, end and entity_id; the description only reinforces the time-window default. The one undocumented parameter, max_items, is not explained anywhere, and no hint is given about what happens when the cap is hit.

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 states a specific verb (List) and two concrete resources (calendar entities, events of one calendar) and makes the mode switch explicit via 'one calendar'. No sibling tool covers calendars, so sibling differentiation is a non-issue; the only small gap is that 'calendar entities' is slightly jargon-y versus 'calendars'.

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: the phrase 'or the events of one calendar' hints that supplying a calendar narrows the call, but the actual rule ('Omit entity_id to list calendars') lives in the schema, not the description. There is no explicit when-to-use or when-not-to-use guidance against alternatives such as search_entities or get_history.

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