Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ICS_URLYesYour public Google Calendar ICS URL (e.g., https://calendar.google.com/calendar/ical/YOUR_CALENDAR_ID/public/basic.ics)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_eventsA
List calendar events within a specific date range, expanding recurring events.

Args:
    start_date: Start of the range (ISO format, e.g., '2023-01-01')
    end_date: End of the range (ISO format)

Returns:
    List of events falling within the range.
search_eventsA
Search for events matching a text query in summary or description.
Note: This searches a wide range (current year +/- 1 year) to be useful, 
as text search on infinite recurrence is impossible without a range.

Args:
    query: The text to search for.

Returns:
    List of matching events.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: list_events retrieves events within a specific date range, while search_events finds events matching a text query across a broader timeframe. There is no overlap in functionality, and the descriptions make the distinction unambiguous.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (list_events and search_events), using snake_case and clear, descriptive verbs. The naming is predictable and aligned with common conventions for such operations.

Tool Count2/5

With only two tools, this server feels severely under-scoped for a calendar domain. Essential operations like creating, updating, or deleting events are missing, making it incomplete for typical calendar management tasks. A calendar server should have at least basic CRUD operations to be functional.

Completeness2/5

The tool surface is significantly incomplete for a calendar server. While list_events and search_events provide read/search capabilities, there are no tools for creating, updating, or deleting events, which are core to calendar management. This leaves major gaps that will hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues