Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

trip

GET /trips/:tripID — Get a single trip

Single-trip read with the full payload. This is the canonical endpoint for "who should I meet on this trip?" — the response embeds a complete discovery block (ranked top-10 picks with AI summaries, the full pool of locals + visitors, events in town, and date-overlapping trips). If you only want the discovery block without the trip body, use GET /trips/:tripID/discovery.

Key discovery fields agents almost always want:

  • discovery.people — ranked top-10 DCers to meet on this trip, each carrying score (higher = better match), mini profile (userID, userName, displayName, photo, headline), reason (local / visiting / event-attendee), overlapDays, detail. Sourced from a vector-search + business-context ranking, not just date overlap.

  • discovery.whyToMeet — AI-written "why you should meet them" paragraph for each of the top-10, keyed by userID, each { text, generatedAt }. The most useful AI signal in the whole trip product — agents should surface this verbatim when introducing a match.

  • discovery.fullPool — every visible DCer travelling or local during the trip window (typically 5–10× larger than /trips/overlaps, which only returns date-window matches). Same row shape as people but no score.

  • discovery.overlappingTrips — other DCers travelling at the same time/place, each with mini profile attached so no second fetch is needed. This is the same data that /trips/overlaps returns, embedded here for convenience.

  • discovery.events — events in the destination city during the trip window.

  • discovery.generatedAt — when the discovery cache was last refreshed.

Also included: points — up to 20 venue/idea notes with optional Google Place data, plus a linked roomID for the auto-created trip coordination room.

Hidden + guest profiles are filtered out from all discovery lists. The discovery block is null for newly-created trips until the background sync task runs (~seconds — call POST /trips/:tripID/refresh to force-recompute). Open to any authenticated DCer (you can read other DCers' trips too).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tripIDYesThe trip ID

TDQS

A4.6/5.0
Behavior5/5

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

No annotations provided, so the description fully carries the burden. It discloses that hidden and guest profiles are filtered out, discovery is null for new trips until background sync, and it is open to any authenticated DCer. 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.

Conciseness4/5

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

The description is well-structured with bullet points for key fields and front-loads the purpose. While comprehensive, it is slightly verbose with multiple nested lists, but every sentence adds value. Could be marginally more concise.

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?

Given the complexity of the response (nested discovery object, many fields) and no output schema, the description is extremely thorough. It covers all key fields: people, whyToMeet, fullPool, overlappingTrips, events, generatedAt, points, roomID, and filtering/sync behavior. Complete and self-contained.

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 only one parameter (tripID). The description does not add semantic detail beyond the schema, but it provides context for the parameter by explaining the endpoint's purpose. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 'GET /trips/:tripID — Get a single trip' and explains the full payload, including the discovery block and key fields. It distinguishes from siblings like trip_discovery and trips_overlaps by noting alternatives for specific needs.

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 this endpoint vs. alternatives: 'If you only want the discovery block without the trip body, use GET /trips/:tripID/discovery.' Also mentions the POST endpoint for forced refresh and that it's open to any authenticated DCer.

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