Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List events on a calendar

calendar_list_events
Read-onlyIdempotent

List events on a specific calendar between a start and end date to view upcoming or past calendar entries.

Instructions

List events on one calendar between start and end.

Calls GET /api/calendars/{entity_id} over HTTP with start/end as query parameters.

Use when: reading a calendar's upcoming or past events for a known date range. Not for: listing the calendar entities themselves — use calendar_list_calendars. Returns: list of event dicts as returned by HA (fields include summary, start, end, uid), or an empty list if the response isn't a JSON list.

Input Schema

NameRequiredDescriptionDefault
endYesRange end as an ISO 8601 datetime, e.g. '2026-05-05T00:00:00'.
startYesRange start as an ISO 8601 datetime, e.g. '2026-04-28T00:00:00'.
entity_idYesCalendar entity ID, e.g. 'calendar.family', from `calendar_list_calendars`.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.1
    • addedInput schema / properties / end / description
      Added value: +"Range end as an ISO 8601 datetime, e.g. '2026-05-05T00:00:00'."
    • addedInput schema / properties / entity_id / description
      Added value: +"Calendar entity ID, e.g. 'calendar.family', from `calendar_list_calendars`."
    • addedInput schema / properties / start / description
      Added value: +"Range start as an ISO 8601 datetime, e.g. '2026-04-28T00:00:00'."
  2. First observedv0.3.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, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the underlying HTTP call shape and a notable fallback behavior (returns an empty list when the response isn't a JSON list), which is genuine context beyond annotations.

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?

Front-loaded with purpose, then endpoint, then usage, then returns — a clean, scannable structure. The HTTP endpoint line is somewhat incidental detail, but every other sentence earns its place.

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?

Despite an output schema existing (so return-value documentation is not strictly required), the description still conveys return shape and the empty-list edge case. An agent has everything needed to call this correctly and interpret results.

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 fully documented with types, required status, and examples. The description only restates start/end as query parameters, adding little beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Specific verb (List) + resource (events) + scope (one calendar, between start and end). It explicitly names the sibling it is not (calendar_list_calendars), so an agent can distinguish it 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?

Uses explicit 'Use when' and 'Not for' structure with a named alternative sibling. Both the positive condition (known date range) and the exclusion (listing calendar entities) are stated, leaving nothing to inference.

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