Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

What's on my calendar

connections_calendar_list
Read-only

Use this when the member asks what is on their calendar or schedule, whether they are free or busy at some time, what they have today, tomorrow or this week, or when something on their calendar is. Returns the events on the member's own Connections calendar in a window, soonest first: the ones they added plus the ones other sources put there (their hosted events, note deadlines, a connected Google Calendar), each with its id, title, starts_at, ends_at, all_day and source. Answer these questions from this list rather than from chat history. The window is from (default now) for days days (default 7, at most 62).

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days the window covers from `from` (1-62, default 7).
fromNoOptional window start, an ISO 8601 date-time with the member's UTC offset (2027-01-15T00:00:00-06:00). Default: now.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).
timezoneNoThe member's IANA time zone, e.g. 'America/Chicago'. With it, times may be plain wall-clock times (2027-01-15T10:00) and the server applies the zone's offset, daylight saving included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days / maximum
      Added value: +62
    • addedInput schema / properties / days / minimum
      Added value: +1
    • addedInput schema / properties / from / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2}(\\.\\d{1,9})?)?(Z|[+-]\\d{2}:?\\d{2})?$"
  2. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "The member's IANA time zone, e.g. 'America/Chicago'. With it, times may be plain wall-clock times (2027-01-15T10:00) and the server applies the zone's offset, daylight saving included.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, and the description still adds substantial context beyond them: the merged-source behavior (hosted events, note deadlines, a linked Google Calendar appear alongside native events), the ordering guarantee ('soonest first'), and the returned field set. It also discloses the window defaults and the 62-day cap, which shapes how the agent should scope queries.

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?

Three sentences ordered sensibly: when to use, what comes back, then the window mechanics. The final sentence largely restates defaults already present in the schema, which is mild redundancy, but every sentence is front-loaded and readable.

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?

With no output schema, the description carries the burden of describing return values, and it does so precisely (id, title, starts_at, ends_at, all_day, source) while also covering merge behavior, ordering, and window bounds. An agent has everything needed to call this correctly and interpret the response.

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 the baseline is 3, but the description goes further by explaining how `from` and `days` compose into a single window and restating the defaults/cap in prose for quick reference. It adds nothing about the delegation parameters `person` and `project`, whose semantics come only from the schema.

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?

States a specific verb and resource — 'Returns the events on the member's own Connections calendar in a window, soonest first' — and explicitly enumerates the merged sources (their own additions, hosted events, note deadlines, connected Google Calendar). This is clearly distinguishable from sibling write tools like connections_calendar_add/update/delete and from the broader connections_events_list.

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

Usage Guidelines4/5

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

The opening clause gives concrete trigger questions ('what is on their calendar', 'whether they are free or busy', 'today, tomorrow or this week') and adds a routing instruction to answer from this list rather than chat history. It does not name alternatives such as connections_events_list or connections_schedule_get_focus_day, so there is no explicit when-not guidance, but the intended use case is unambiguous.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources