GET /virtual-events — List Live Calls
Returns upcoming Live Calls (online sessions like Connect Calls, Happy Hour, Welcome Call, plus DC BLACK-only calls). Add ?past=true to include past calls.
| Name | Required | Description | Default |
|---|---|---|---|
| past | No | Include past Live Calls. | |
| limit | No | Max results (1-100). | |
| cursor | No | Cursor from a previous response's `nextCursor`. Pass to fetch the next page. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It mentions the past parameter but fails to describe read-only nature, pagination behavior (cursor is in schema but not explained), or authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler; front-loaded with key verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Lacks return value description and pagination behavior details; adequate for basic use but incomplete for an endpoint with cursor and no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all 3 params with descriptions; description adds context that past parameter toggles between upcoming/past results, enhancing meaning beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'List Live Calls' with specific examples (Connect Calls, Happy Hour, etc.) and distinguishes from siblings like virtual_event (singular) and events (physical).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for listing upcoming virtual events but does not explicitly compare to siblings (e.g., events for physical events) or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Despite the large number of tools, each has a detailed description that clearly distinguishes its purpose. Minor potential overlaps (e.g., search vs. resource-specific search, own vs. other's agenda) are well documented, so an agent can differentiate them.
Tool names follow a consistent verb_noun or resource_subresource_action pattern in snake_case. A few tools are just nouns (e.g., 'alerts', 'announcements'), but these are top-level listing endpoints; overall the naming is predictable.
85 tools is very high for a single server, making it difficult for an agent to efficiently explore and select the right tool. While each tool seems justified for the broad domain, the count feels overwhelming and could be streamlined.
The tool surface covers most major areas (events, trips, chapters, rooms, search, profile, etc.) with CRUD or lifecycle operations. However, the lack of a 'send message' tool for rooms is a notable gap, and some resources (e.g., events) are read-only on creation/update, limiting agent workflows.
