Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

event_free_slots_create

POST /events/:eventID/free-slots — Find shared free time slots across attendees

Computes shared free slots across a set of event attendees — the time windows where they're NOT in a bookmarked session or meetup. Use to find a coffee window with one DCer, or a junto-style lunch slot for a group.

Body: userIDs[] (1-20), minDurationMinutes (default 30, min 15, max 480), optional eventDayDate: YYYY-MM-DD to scope to a single event day.

Slot grid: derived from the event's session schedule, partitioned into minDurationMinutes windows. For each window we subtract each user's bookmarked sessions + meetup RSVPs.

Sort: slots ranked by len(freeFor) desc — fully-shared windows first, then partial overlaps.

Auth: caller must hold a valid ticket. Non-attendee IDs are silently dropped.

⚠️ WRITE operation: this mutates your DC account data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIDYesEvent ID
userIDsYesAttendee userIDs to compare (1-20). Non-attendees silently dropped.
eventDayDateNoOptional. Scope to a single event day (YYYY-MM-DD venue-local). Omit for the full event range.
minDurationMinutesNoMinimum slot duration in minutes (default 30, range 15-480)

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: it is a WRITE operation that mutates account data, silently drops non-attendees, explains slot derivation from session schedule, and details sorting logic. 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 front-loaded endpoint and purpose, followed by parameter details, algorithm, sorting, auth, and warning. Every sentence adds value without redundancy.

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 complex tool with no output schema, the description sufficiently covers algorithm, sorting, auth requirements, and side effects. User can understand what the tool does and how to use it correctly.

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 baseline 3. Description adds default values, min/max constraints for minDurationMinutes, and clarifies that non-attendee IDs are silently dropped, providing additional context beyond the parameter descriptions.

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 'Find shared free time slots across attendees' with a specific endpoint and verb. It distinguishes from sibling tools like event_schedule_bookmark or event_agenda by focusing on free slot computation.

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?

Provides explicit usage examples ('find a coffee window with one DCer, or a junto-style lunch slot for a group') and implies context, but does not explicitly contrast with alternative tools or state when not to use.

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