Skip to main content
Glama

Read the calendar

get_calendar
Read-onlyIdempotent

The member's calendar, events, invitations found in mail, the job search schedule, and the page where the member connects a Google or Microsoft calendar. Actions: view, export_ics, event, event_context, mail_invitations, schedule, schedule_sources, time_budget, connect_link. 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": "get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
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: -[
      -  "view",
      -  "export_ics",
      -  "event",
      -  "event_context",
      -  "mail_invitations",
      -  "schedule",
      -  "schedule_sources",
      -  "connect_link",
      -  "help"
      -]New value: +[
      +  "view",
      +  "export_ics",
      +  "event",
      +  "event_context",
      +  "mail_invitations",
      +  "schedule",
      +  "schedule_sources",
      +  "time_budget",
      +  "connect_link",
      +  "help"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "view",
      -  "export_ics",
      -  "event",
      -  "event_context",
      -  "mail_invitations",
      -  "schedule",
      -  "schedule_sources",
      -  "help"
      -]New value: +[
      +  "view",
      +  "export_ics",
      +  "event",
      +  "event_context",
      +  "mail_invitations",
      +  "schedule",
      +  "schedule_sources",
      +  "connect_link",
      +  "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."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is carried. The description adds the useful "help" discovery mechanism but says nothing about what the divergent actions return or require — export_ics presumably produces serialized calendar content, and connect_link presumably produces an OAuth URL, yet neither is characterized.

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

Conciseness4/5

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

The action enumeration is front-loaded and essential for a nine-action tool, with no filler sentences. The opening clause is an awkward noun list rather than a purpose statement, but it is information-dense and short enough not to hinder scanning.

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 tool with nine heterogeneous actions, a generic params blob, and no output schema, the definition covers scope but not behavior per action. The "help" escape hatch partly compensates, but an agent must make a discovery call before it can confidently choose between, say, time_budget and schedule, or between event and event_context.

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 coverage is 75% and both id parameters have precise pattern-and-provenance descriptions, so the schema carries most of the load. The description points at the "help" action for the free-form params object, but that pointer is already present in the schema's own params description, so it adds little beyond what is structured.

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 definition names the resource domain precisely (calendar, events, mail invitations, job-search schedule, connect page) and enumerates nine concrete actions that pin down scope, so an agent knows what is inside. It never states what separates it from the sibling manage_calendar, which is the only thing keeping 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?

Usage is only implied: the action names (view, export_ics, event_context, connect_link) suggest intent, and the definition sensibly routes the agent to action "help" for field-level detail. There is no explicit when-to-use-this-vs-manage_calendar guidance, no statement that this tool never mutates, and no note that connect_link initiates an account connection rather than reading data.

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.