Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

event_meetups

GET /events/:eventID/meetups — List event meetups

Returns the approved member-organized meetups for an event, sorted chronologically. Only approved meetups are returned.

Access: any active DCer who can see the event can view approved meetup listings + attendee lists. Only RSVPing to a meetup (and the resulting chat-channel access) requires a valid ticket.

Time-zone handling: meetups use explicit wall-clock fields (date = YYYY-MM-DD, startTime / endTime = HH:mm) plus the event's timezone (IANA). Pair them when localizing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIDYesEvent ID

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, but the description fully covers behavior: only approved meetups returned, chronological sorting, time-zone handling with wall-clock fields and IANA timezone. Also discloses access rules and what requires a ticket. No contradictory information.

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 headings and bullet points. Every sentence adds value: endpoint path, behavior, access, time-zone handling. No redundancy. Efficient use of space.

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?

For a simple listing tool with one parameter and no output schema, the description covers everything an agent needs: purpose, access conditions, filtering, sorting, and time-zone handling. Sibling tools fill gaps for related actions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with eventID described as 'Event ID'. Description does not add semantic detail beyond the schema, but the context of listing meetups for that event is clear. Appropriate baseline score.

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?

The description clearly states the tool lists approved member-organized meetups for an event, sorted chronologically. The verb 'List' and resource 'event meetups' are explicit. It distinguishes from sibling tools like event_meetup_attendees and event_meetup_rsvp.

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?

Explicitly states when to use: 'Returns the approved member-organized meetups for an event'. Specifies access conditions (any active DCer who can see the event) and limitations (only approved meetups). Implicitly differentiates from RSVP and attendee listing tools.

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