Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

My events

connections_events_list
Read-only

Use this when the member asks about the events they host, what is coming up that they are hosting, or their upcoming hosted events (for what is on their own calendar, use connections_calendar_list). Returns the member's hosted events on Connections across every workspace they have - unfinished ones by default, soonest first, each with its date, location, public link and the workspace it is in. Pass project to list one workspace's events only. With upcoming (the default) and no status, only live events (published and draft) are listed - never canceled or archived ones; pass status (published, draft, canceled, archived, or a list of them) to list those instead, e.g. status 'canceled' for the called-off events. For one event's guests and settings use connections_event_get.

Input Schema

NameRequiredDescriptionDefault
limitNoMax events to return (1-100, default 20).
queryNoOptional topic filter over an event's title and location ('demo day', 'houston'). Words are scored, not AND-ed.
detailNocompact (default) = the fields most questions need. full = every field this tool shapes, including registration windows and the description.
fieldsNoOptional: return only these field names on each event. Wins over `detail` when given.
offsetNoHow many matching events to skip first, for paging. Default 0.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
statusNoOptional: list only events in this status (or any of these). Overrides the live-only default of upcoming.
projectNoWorkspace to run this call in (id or name).
upcomingNotrue (default) = only events that have not ended yet, soonest first, and (unless `status` is given) only published and draft ones. false = every event of any status, most recent first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / status
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "published",
+        "draft",
+        "canceled",
+        "archived"
+      ],
+      "type": "string"
+    },
+    {
+      "items": {
+        "enum": [
+          "published",
+          "draft",
+          "canceled",
+          "archived"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Optional: list only events in this status (or any of these). Overrides the live-only default of upcoming."
+}
    • changedInput schema / properties / upcoming / description
      Previous value: -"true (default) = only events that have not ended yet, soonest first. false = every event, most recent first."New value: +"true (default) = only events that have not ended yet, soonest first, and (unless `status` is given) only published and draft ones. false = every event of any status, most recent first."
  2. 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, but the description adds real behavior: the live-only default (published + draft, never canceled/archived), the sort order in both upcoming modes, and the override rules for status. It doesn't discuss pagination limits or result caps beyond the `limit` schema, which keeps it short of a 5.

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?

Front-loaded with the trigger and the negative case in the first sentence, and the default/override logic follows logically. The second and third sentences are dense run-ons that could be split for scanability, but nothing is redundant.

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?

Nine optional parameters with no output schema, yet the description covers what each result contains, the default filter, sort order, and workspace scoping — everything needed to call it correctly. Remaining details (limit range, detail enum) are fully documented in the schema.

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 a 3, but the description earns more by explaining the interaction between parameters the schema states individually: upcoming+no-status means live-only, status overrides that default, and project narrows to one workspace. The `query`, `detail`, and `fields` semantics are left entirely to 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 resource and scope: the member's hosted events across every workspace, soonest first, with the fields returned. It explicitly distinguishes itself from connections_calendar_list (own calendar) and connections_event_get (single event's guests/settings), so an agent can route without opening a schema.

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?

Opens with the trigger condition ('when the member asks about the events they host...') and names both alternatives with their selecting condition. It also gives a worked example of the status filter ('status canceled for the called-off events'), leaving little to inference.

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