local-mcp

Update Calendar Event

update_calendar_event

Updates an existing event in the Mac's Calendar app (Calendar.app) by ID. Pass only the fields you want to change — unspecified fields are left as-is. Get the event_id from list_calendar_events. For Microsoft 365 use the m365 calendar tools instead.

Input Schema

TableJSON Schema

Name	Required	Description
`span`	No	For recurring events: 'this' (default) or 'future'
`notes`	No	New notes — pass empty string to clear (optional)
`title`	No	New title (optional)
`confirm`	No	Must be true to apply changes
`end_date`	No	New end datetime ISO 8601 (optional). Same timezone rules as start_date.
`event_id`	Yes	Event identifier from list_calendar_events
`location`	No	New location — pass empty string to clear (optional)
`start_date`	No	New start datetime ISO 8601 (optional). No timezone = Mac's local time; append Z/offset to pin the zone.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`end`	No
`notes`	No
`start`	No
`title`	No
`all_day`	No
`updated`	No
`calendar`	No
`location`	No
`attendees`	No
`calendar_id`	No
`attendees_total`	No

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description additionally clarifies the partial-update behavior (unspecified fields left as-is), which is useful. It does not mention the `confirm` flag requirement, though that is covered in the schema.

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?

Three sentences, front-loaded with the core action, followed by usage guidance and cross-service disambiguation. No filler or redundancy.

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?

Given the tool's complexity (8 params, output schema present), the description covers the most important context: partial update semantics, ID source, and service boundary. It wisely omits return-value details since an output schema exists. Minor omission: no mention of the `confirm` parameter requirement, but that is in the schema.

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 coverage is 100%, but the description adds crucial semantics: 'Pass only the fields you want to change — unspecified fields are left as-is' directly instructs how to use the optional parameters. It also explains where to get event_id, going beyond individual schema descriptions.

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 uses a specific verb ('Updates') and resource ('existing event in the Mac's Calendar app (Calendar.app) by ID'), making the function clear. It distinguishes from create/delete and explicitly mentions the m365 alternative for a different service.

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?

Provides explicit guidance: pass only fields to change, get event_id from list_calendar_events, and use m365 calendar tools for Microsoft 365. This gives clear when-to-use and alternative context.

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

All local-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Update Calendar Event

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources