F
licenseNot graded
qualityC
maintenanceExposes Google Calendar as a tool for Claude Desktop, allowing natural-language queries about your schedule by listing upcoming events via the Google Calendar API.
-
loom-plan
by denislamard
Related Servers
Alternatives to loom-plan
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceIntegrates Google Calendar and Notion to enable Claude to manage your schedule, plan tasks, detect conflicts, and keep appointments and tasks synchronized.17GPL 2.0
- AlicenseNot gradedqualityCmaintenanceEnables read/write access to Google Docs, Sheets, Drive, and Calendar through Claude Desktop, with 24 tools for creating, editing, searching, and managing files and events.1,091 npmMIT
- AlicenseAqualityCmaintenanceEnables Claude to read, create, update, and delete Google Calendar events directly through natural language.685 npmMIT
- FlicenseBqualityCmaintenanceConnects Claude to Google Tasks, enabling users to list, create, update, complete, reopen, and delete tasks through natural language.9-
- FlicenseNot gradedqualityDmaintenanceConnects Claude Desktop to Google Calendar for local calendar management including adding, updating, and deleting events, checking schedules, and calculating travel time between meetings.1-
TDQS
A4.1/5.0
Scored across 13 tools
Disambiguation4/5
The read tools overlap in scope: `next` aggregates `overdue`, `agenda`, `tasks`, and `free_slots`, while `agenda`, `tasks`, and `find` cover intersecting data. The descriptions explicitly clarify intended use cases (daily overview vs. unfinished items vs. arbitrary window vs. search), so an agent can usually choose correctly, but the boundaries require careful reading.
Naming Consistency3/5
Read tools use bare nouns or adjectives (`next`, `agenda`, `tasks`, `overdue`, `containers`, `free_slots`) while write tools use verb_noun or verb patterns (`add_event`, `update_task`, `set_status`, `delete`). This is readable and arguably intentional as a read/write split, but it is not a single predictable naming convention.
Tool Count5/5
13 tools is well within the ideal 3–15 range for a personal calendar and task assistant. Each tool covers a distinct operation—daily overview, search, availability, CRUD for events and tasks—so none feels superfluous.
Completeness5/5
The surface provides full lifecycle coverage: create, read, update, delete, and status changes for both events and tasks, plus search, free-slot calculation, and container discovery. No obvious domain operation is missing for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues