Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

virtual_event_attendees

GET /virtual-events/:sessionID/attendees — List Live Call attendees

List the attendees of a Live Call — the DCers who RSVPd yes or maybe (the same set behind attendeeCount, mirroring how GET /events/:eventID/attendees counts RSVPs). Profiles use the standard other-person shape (identical to GET /events/:eventID/attendees and GET /profile-match): public fields plus privacy-gated annualRevenue + teamSize where the member shares them. Hidden and guest profiles are filtered out.

Access: any active DCer who can see the Live Call. DC BLACK-only calls stay tier-gated — DC-tier callers get tier_restricted (403).

Pagination: page with ?limit= (1-100, default 100) plus the opaque ?cursor= from the previous response's nextCursor (null when there are no more).

See GET /virtual-events/:sessionID for the call itself, and GET /events/:eventID/attendees for the in-person equivalent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-100).
cursorNoCursor from a previous response's `nextCursor`. Pass to fetch the next page.
sessionIDYesThe Live Call session ID. Find IDs via `GET /virtual-events`.

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, so description fully covers behavior: pagination details, access control, profile shape, filtering of hidden/guest profiles, and relationship to other endpoints. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with headers for access and pagination, front-loads the main purpose, and no superfluous sentences.

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?

No output schema, but description explains return shape (profile fields, optional privacy-gated data) and pagination cursor. References related endpoints for additional context.

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%, but description adds context: sessionID source from GET /virtual-events, limit default and range, and cursor usage for pagination. Adds marginal value over 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?

Clearly states the function: list attendees of a Live Call. Includes specific verb 'list', resource 'attendees', and distinguishes from sibling tools like event_attendees and virtual_event.

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?

Provides explicit guidance: when to use (for Live Call attendees), alternatives (in-person equivalent, call details endpoint), and access constraints (tier-gated, filtered profiles).

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

All DC Member API toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness3/5

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.

Resources