List calendars
well_list_calendarsList the calendars connected to this workspace, with their owner. Use it to pick the calendar for a new event: events can only be created on a calendar with is_mine true, and the user's main calendar has is_primary true. owner_person_id is the member whose own calendar it is. It is null on a calendar shared with a member: that member can read it but does not own it, and Well does not know who owns it, so never name an owner for it. Only the public events of a shared calendar can be read, and it cannot be changed through Well. account_email is the Google account the caller's own calendar syncs from (null on another member's calendar), so an answer can name the account. It also gives the calendar_id that well_list_calendar_events takes to read one calendar. If the result has a note, give it to the user as it is: it invites them to connect their own calendar.
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
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Target 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_id | No | The 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. | |
| workspace_scope | No | 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. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | ||
| error | No | ||
| success | Yes | ||
| calendars | Yes | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | 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. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |