Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official

Get Calendar Events

ha_config_get_calendar_events
Read-onlyIdempotent

Retrieve calendar events from any Home Assistant calendar entity, with customizable start and end times and a maximum result limit.

Instructions

Retrieve calendar events from a calendar entity.

Retrieves calendar events within a specified time range.

Parameters:

  • entity_id: Calendar entity ID (e.g., 'calendar.family')

  • start: Start datetime in ISO format (default: now)

  • end: End datetime in ISO format (default: 7 days from start)

  • max_results: Maximum number of events to return (default: 20)

Example Usage:

# Get events for the next week
events = ha_config_get_calendar_events("calendar.family")

# Get events for a specific date range
events = ha_config_get_calendar_events(
    "calendar.work",
    start="2024-01-01T00:00:00",
    end="2024-01-31T23:59:59"
)

Note: To find calendar entities, use ha_search(query='calendar', domain_filter='calendar')

Returns:

  • List of calendar events with summary, start, end, description, location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd datetime in ISO format (default: 7 days from start)
startNoStart datetime in ISO format (default: now)
entity_idYesCalendar entity ID (e.g., 'calendar.family')
max_resultsNoMaximum number of events to return

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description details defaults for start/end, max_results, and the return format (list with fields). This adds operational context not captured by annotations.

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?

The description is well-structured with clear sections: purpose, parameters, example, note, and returns. It is concise and front-loaded, every sentence adds value.

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

Completeness5/5

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

Given the low complexity, full schema coverage, and presence of output schema, the description is complete. It explains purpose, parameters, defaults, example usage, and suggests how to find entity IDs.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description repeats schema descriptions but adds practical context through example usage and a note on finding entities, which provides extra meaning for an AI agent.

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 clearly states the verb 'Retrieve' and the resource 'calendar events' from a calendar entity. It is distinct from sibling tools 'ha_config_remove_calendar_event' and 'ha_config_set_calendar_event', making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides a note on finding calendar entities via 'ha_search' and shows example usage. While it does not explicitly state when not to use, the context of read-only operation is clear from annotations and sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/homeassistant-ai/ha-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server