Skip to main content
Glama

Chronary

by ai.chronary

update_event

Reschedule or edit an event — change its title, description, start/end times, location, status, reminders, or metadata. Use this to move an appointment to a new time or update its details. Provide only the fields you want to change. Holds cannot be edited via this tool (use confirm_event / release_event). External iCal events are read-only. calendar_id is optional — if omitted it is resolved from the event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew event title
statusNoNew event status
all_dayNoWhether this is an all-day event
end_timeNoNew end time (ISO 8601)
event_idYesEvent ID to update
metadataNoReplacement metadata object
remindersNoReminder offsets in minutes before start_time. Omit to leave unchanged, null to inherit the calendar default, [] for no reminders.
start_timeNoNew start time (ISO 8601)
calendar_idNoCalendar ID that owns the event. Optional — if omitted the calendar is resolved from the event.
descriptionNoNew description, or null to clear it
recurrence_ruleNoSet/change the recurring series rule (RFC 5545 RRULE subset, full-series semantics), or null to make the event a one-off. Changing the rule or start_time resets cancelled occurrences.

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses partial-update behavior ('Provide only the fields you want to change') and constraints (holds not editable, external iCal read-only). Could add more on success/failure behavior or idempotency.

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?

Concise two core sentences plus additional context for constraints and optional parameters. Front-loaded with purpose, no fluff.

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?

Given 11 parameters, nested objects, and no output schema, the description covers all essential aspects: editable fields, partial update, constraints, optional parameter behavior. Complete for agent usage.

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

Parameters4/5

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

Schema has 100% description coverage (baseline 3). The description adds value by summarizing editable fields, explaining calendar_id optionality, and clarifying reminder mechanics (omit/null/[]).

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 clearly states the tool reschedules or edits events, listing specific fields (title, description, times, etc.). It distinguishes from siblings by noting that holds require confirm_event/release_event and external iCal events are read-only.

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?

Explicit when-to-use: rescheduling/editing events. When-not-to: for holds (use confirm_event/release_event) and external iCal events. Also explains optional calendar_id resolution.

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

All Chronary toolsInspect
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.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions that differentiate overlapping operations like cancel_event vs release_event and find_meeting_time vs get_availability.

Naming Consistency5/5

All 54 tools follow a consistent verb_noun pattern in snake_case (e.g., create_calendar, list_events, delete_webhook), with no mixing of styles or vague verbs.

Tool Count2/5

With 54 tools, the server is over-scoped; the rubric considers 25+ tools as 'too many' for typical purposes, making navigation and selection harder without justification for such granularity.

Completeness5/5

The toolset provides full CRUD for agents, calendars, events, booking pages, proposals, webhooks, and iCal subscriptions, plus specialized operations like hold management, proposal resolution, and admin functions, leaving no obvious gaps.

Resources