Skip to main content
Glama

Manage the calendar

manage_calendar
Destructive

Create and connect calendars, add, change and delete events, prepare replies to invitations and manage the job search schedule. Events are written to the member's own calendars; no invitations are sent. Actions: create_local, connect_caldav, import_ics, sync, choose_calendar, create_event, update_event, delete_event, hide_interview_event, prepare_rsvp, import_invitation, disconnect, update_schedule, generate_schedule, approve_schedule, discard_schedule, set_time_budget. Call with action "help" for each action's fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe item's key as the matching list answered it.
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
mail_message_idNoA received message's id: its Mailbox id (i-…) or the same id without "i-" (a calendar event's or RSVP draft's mailMessageId); either works.
calendar_event_idNoA calendar event's id from get_calendar view (events[].id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create_local",
      -  "connect_caldav",
      -  "import_ics",
      -  "sync",
      -  "choose_calendar",
      -  "create_event",
      -  "update_event",
      -  "delete_event",
      -  "hide_interview_event",
      -  "prepare_rsvp",
      -  "import_invitation",
      -  "disconnect",
      -  "update_schedule",
      -  "generate_schedule",
      -  "approve_schedule",
      -  "discard_schedule",
      -  "help"
      -]New value: +[
      +  "create_local",
      +  "connect_caldav",
      +  "import_ics",
      +  "sync",
      +  "choose_calendar",
      +  "create_event",
      +  "update_event",
      +  "delete_event",
      +  "hide_interview_event",
      +  "prepare_rsvp",
      +  "import_invitation",
      +  "disconnect",
      +  "update_schedule",
      +  "generate_schedule",
      +  "approve_schedule",
      +  "discard_schedule",
      +  "set_time_budget",
      +  "help"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create_local",
      -  "connect_caldav",
      -  "import_ics",
      -  "sync",
      -  "choose_calendar",
      -  "create_event",
      -  "update_event",
      -  "delete_event",
      -  "prepare_rsvp",
      -  "import_invitation",
      -  "disconnect",
      -  "update_schedule",
      -  "generate_schedule",
      -  "approve_schedule",
      -  "discard_schedule",
      -  "help"
      -]New value: +[
      +  "create_local",
      +  "connect_caldav",
      +  "import_ics",
      +  "sync",
      +  "choose_calendar",
      +  "create_event",
      +  "update_event",
      +  "delete_event",
      +  "hide_interview_event",
      +  "prepare_rsvp",
      +  "import_invitation",
      +  "disconnect",
      +  "update_schedule",
      +  "generate_schedule",
      +  "approve_schedule",
      +  "discard_schedule",
      +  "help"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create_local",
      -  "connect_caldav",
      -  "connect_link",
      -  "import_ics",
      -  "sync",
      -  "choose_calendar",
      -  "create_event",
      -  "update_event",
      -  "delete_event",
      -  "prepare_rsvp",
      -  "import_invitation",
      -  "disconnect",
      -  "update_schedule",
      -  "generate_schedule",
      -  "approve_schedule",
      -  "discard_schedule",
      -  "help"
      -]New value: +[
      +  "create_local",
      +  "connect_caldav",
      +  "import_ics",
      +  "sync",
      +  "choose_calendar",
      +  "create_event",
      +  "update_event",
      +  "delete_event",
      +  "prepare_rsvp",
      +  "import_invitation",
      +  "disconnect",
      +  "update_schedule",
      +  "generate_schedule",
      +  "approve_schedule",
      +  "discard_schedule",
      +  "help"
      +]
    • changedInput schema / properties / mail_message_id / description
      Previous value: -"A received message's id: a calendar event's mailMessageId, or a Mailbox message id (i-…) without its leading \"i-\"."New value: +"A received message's id: its Mailbox id (i-…) or the same id without \"i-\" (a calendar event's or RSVP draft's mailMessageId); either works."
  4. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is mostly covered. The description adds useful context that events are written only to the member's own calendars and that no invitations are sent. It does not disclose which actions are destructive, whether deletes are reversible, or what connect/disconnect/sync entail, so it remains only adequate beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the purpose and an important behavioral caveat, which is good structure. However, it then duplicates the full action enum from the input schema and adds little explanatory value for that space. It is not bloated with fluff, but the redundant action list keeps it from being fully concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex multi-action tool with 18 action values, a nested params object, destructive behavior, and no output schema, the description covers scope and the key no-invitation side effect. It also points agents to action 'help' for per-action fields, which is useful. It still lacks per-action semantics and return behavior, so it is only adequately complete rather than fully self-sufficient.

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

Parameters3/5

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

Schema description coverage is high at 80%, so the schema already documents key parameters such as mail_message_id and calendar_event_id. The description duplicates the action enum and repeats the 'help' mechanism already stated in the params schema description. With high schema coverage, a baseline 3 is appropriate because the description adds little parameter meaning beyond the structured fields.

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?

The description states a clear set of management verbs and resources: creating/connecting calendars, adding/changing/deleting events, preparing replies, and managing the job search schedule. It also enumerates all supported actions, so an agent can understand the tool's broad scope without opening the schema. It does not explicitly name or differentiate from the likely read-oriented sibling get_calendar, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through its action list and distinguishes preparation from sending via 'prepare replies' and 'no invitations are sent.' However, it gives no explicit when-to-use guidance, exclusions, or named alternatives such as get_calendar for viewing events. The guidance is therefore only minimally viable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.