Skip to main content
Glama
ReinforceZwei

trilium-calendar-mcp

by ReinforceZwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

calendar_list_events

List calendar events stored as Trilium notes, optionally filtered by date range, title, location, or categories. Retrieve events for scheduling or analysis.

Instructions

List events, optionally filtered by date range and text.

Args: calendar_name: Calendar to read; omit to use the default calendar. start_date: Earliest day to return, YYYY-MM-DD (events overlapping the range are included). end_date: Latest day to return, YYYY-MM-DD. limit: Maximum number of events to return (0 = no limit). title_contains: Only events whose title contains this text. categories: Comma-separated categories; matches events carrying any of them. location_contains: Only events whose location contains this text. include_descriptions: Fetch event bodies (one extra request per event). search_all_calendars: Search every configured calendar instead of one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
end_dateNo
categoriesNo
start_dateNo
calendar_nameNo
title_containsNo
location_containsNo
include_descriptionsNo
search_all_calendarsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior: overlapping events are included in the date range, and include_descriptions costs one extra request per event. However, it says nothing about permissions, pagination, or what the returned records look like.

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 purpose sentence followed by a tight, scannable Args block. Every line is necessary given 0% schema coverage; no filler or repetition.

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 nine-parameter, zero-annotation, no-output-schema tool, the description covers parameters and key behaviors well. It omits any indication of the return shape or result ordering, but the core invocation information is present.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does for all nine parameters: formats (YYYY-MM-DD), defaults-by-omission (default calendar), sentinel values (limit 0 = no limit), and matching semantics (overlap for dates, contains for text, any-of for categories). This adds real meaning beyond the bare schema titles and types.

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?

States a clear verb+resource ('List events') and names the two filtering axes (date range, text). It is distinguishable from mutating siblings, but it does not explicitly differentiate itself from close read siblings like calendar_get_upcoming_events or calendar_get_event.

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 explicit when-to-use guidance or routing to alternatives. The reader must infer that this is the broad listing tool versus calendar_get_upcoming_events or calendar_get_event. No prerequisites or exclusions 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