Skip to main content
Glama

List calendar events

well_list_calendar_events
Read-only

List the calendar events inside a time range, in start order. Use it when the user asks what is on their calendar, who they meet and when, or before changing an event. A repeating event is expanded into its occurrences inside the range. It returns the events visible to the whole workspace plus the user's own private ones, never another member's private events. Each event has an event_id; a repeating event's occurrences also carry occurrence_start, which well_update_calendar_event and well_delete_calendar_event take to change just that one. To read only the caller's own calendars, pass mine_only: true. Guests are not listed: call well_get_calendar_event for one event's guests. If the result has a note, give it to the user as it is: it invites them to connect their own calendar.

local_start and local_end are the person's own date, weekday and time of the event. my_response is "declined" when the caller declined the event, else null: a declined event is not a meeting the caller goes to.

The result's connection describes the user's own calendar. Its state is one of "connected" (say nothing about it), "syncing" (the first sync has not finished: say the result can be incomplete), "stale" (say the result can be out of date and give last_synced_at as the time of the last update), "needs_reconnect" (say Well lost access to the calendar, that the result holds only what was synced before, and give reconnect_link once) or "not_connected" (say the user's own calendar is not connected and give reconnect_link once, unless the note already gave it). When the state is not "connected", never call the result complete or up to date, and never call a time free on its strength alone. A null connection means the state could not be read: say nothing about it.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Read the calendar. Write the from and to of a range with the user's UTC offset from well_convert_time, never an offset you worked out.

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the time range, after from; at most 366 days later
fromYesStart of the time range, a timestamp with an offset such as 2026-10-12T00:00:00+02:00
mine_onlyNotrue: only the caller's own calendars, in every workspace the read covers; it replaces owner_person_id, whose id names a member of one workspace only
calendar_idNoOnly this calendar, from well_list_calendars
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
owner_person_idNoOnly the calendars of this workspace member; send the caller's own person id to see just their calendar
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
noteYes
errorNo
eventsYes
successYes
truncatedYes
connectionYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / events / items / properties / local_end
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "date": {
      +      "type": "string"
      +    },
      +    "time": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "weekday": {
      +      "enum": [
      +        "mon",
      +        "tue",
      +        "wed",
      +        "thu",
      +        "fri",
      +        "sat",
      +        "sun"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "weekday",
      +    "time"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / events / items / properties / local_start
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "date": {
      +      "type": "string"
      +    },
      +    "time": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "weekday": {
      +      "enum": [
      +        "mon",
      +        "tue",
      +        "wed",
      +        "thu",
      +        "fri",
      +        "sat",
      +        "sun"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "weekday",
      +    "time"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / events / items / properties / my_response
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": "declined",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed21 schema fields changed
    • changedInput schema / properties / from / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • changedInput schema / properties / to / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • changedOutput schema / properties / connection / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "last_synced_at": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "reconnect_link": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "state": {
      -        "enum": [
      -          "connected",
      -          "syncing",
      -          "stale",
      -          "needs_reconnect",
      -          "not_connected"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "state",
      -      "last_synced_at",
      -      "reconnect_link"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "last_synced_at": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "reconnect_link": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "state": {
      +        "enum": [
      +          "connected",
      +          "syncing",
      +          "stale",
      +          "needs_reconnect",
      +          "not_connected"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "state",
      +      "last_synced_at",
      +      "reconnect_link"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / events / items / properties / conference_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / conference_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / html_link / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / html_link / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / location / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / location / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / occurrence_start / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / occurrence_start / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / timezone / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / timezone / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / events / items / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / events / items / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / note / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / note / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. Start the reply with one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."New value: +"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."
  4. Changed3 schema fields changed
    • addedInput schema / properties / mine_only
      Added value: +{
      +  "description": "true: only the caller's own calendars, in every workspace the read covers; it replaces owner_person_id, whose id names a member of one workspace only",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / connection
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "last_synced_at": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "reconnect_link": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "state": {
      +          "enum": [
      +            "connected",
      +            "syncing",
      +            "stale",
      +            "needs_reconnect",
      +            "not_connected"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "state",
      +        "last_synced_at",
      +        "reconnect_link"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "events",
      -  "truncated",
      -  "note",
      -  "success"
      -]New value: +[
      +  "events",
      +  "truncated",
      +  "note",
      +  "connection",
      +  "success"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / workspace_scope
      Added value: +{
      +  "description": "Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.",
      +  "enum": [
      +    "family"
      +  ],
      +  "type": "string"
      +}
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint/destructiveHint false), yet the description adds substantial context annotations cannot carry: recurring events are expanded into occurrences, visibility is limited to workspace events plus the caller's private ones (never other members' private), and the five connection states each get explicit phrasing rules. It also discloses the note/reconnect_link behavior and the 'never call a time free on its strength alone' caveat.

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?

Purpose and sibling routing are front-loaded, and paragraphs are organized by concern (scope, occurrence model, connection states, workspace routing, timestamp format). It runs long and repeats some parameter guidance already in the schema, but nearly every sentence carries actionable instruction, so little is truly wasted.

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?

For an 8-parameter read tool with an output schema and full annotation coverage, the definition covers everything an agent needs: time-range format, recurrence expansion, visibility boundaries, connection-state recovery messaging, and multi-workspace selection. Return-value shape is left to the output schema as permitted.

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 coverage is 100%, so baseline is 3, but the description adds workflow meaning the schema lacks: it directs use of well_convert_time to derive the from/to offset ('never an offset you worked out'), explains occurrence_start is the handle for well_update/delete of a single occurrence, and recommends mine_only for own-calendar reads. That is real added semantics beyond the schema strings, short of exhaustive coverage.

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 opening sentence names a specific verb and resource and adds scope ('inside a time range, in start order'), and later sentences explicitly distinguish this tool from well_get_calendar_event (guests), well_list_calendars (calendar ids), and the update/delete siblings. An agent can tell exactly what this does and what it is not.

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?

The description states when to reach for it ('what is on their calendar, who they meet and when, or before changing an event') and routes the agent elsewhere by condition: guests require well_get_calendar_event, own-calendars-only requires mine_only: true, single-workspace tokens call directly while multi-workspace tokens must pass workspace_id. Alternatives and preconditions are explicit rather than inferred.

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.

Resources