Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

trip_discovery

GET /trips/:tripID/discovery — Get the discovery block for a trip

Discovery-only read for a trip. Returns the same discovery block as GET /trips/:tripID (people, fullPool, whyToMeet, events, overlappingTrips) without the trip body. Useful for callers that just want "who should I meet on this trip?" — the AI agent gets the ranked top-10 + their whyToMeet paragraphs in a single request.

Use ?include= to subset the response — comma-separated from people,fullPool,whyToMeet,events,overlappingTrips. Default is all. Common patterns:

  • ?include=people,whyToMeet — top-10 picks + their AI-written "why you should meet them" paragraphs (keyed by userID, each carrying { text, generatedAt })

  • ?include=fullPool — every visible DCer travelling/local during the trip window

  • ?include=events — just events in the destination city during the trip window

Open to any authenticated DCer; hidden + guest profiles are filtered out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tripIDYesThe trip ID
includeNoOptional. Comma-separated subset of `people,fullPool,whyToMeet,events,overlappingTrips`. Default = all five.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, but the description discloses read-only behavior, authentication requirements ('Open to any authenticated DCer'), and filtering of hidden/guest profiles. This gives sufficient transparency for a safe read operation.

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 moderately long but well-structured. It starts with the endpoint and purpose, then explains the return value, then details the include parameter with bullet patterns. Every sentence adds value; there is no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description compensates by listing the fields in the discovery block and explaining the effect of the include parameter. It covers the main use case and common scenarios. For a read tool with filtering capability, this is sufficient.

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 is 3. The description adds value by explaining the include parameter in detail: listing options, default behavior, and common patterns with examples. This goes beyond the schema's terse description and helps the agent use the parameter effectively.

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 it is a GET endpoint returning the discovery block for a trip. Distinguishes itself from GET /trips/:tripID by explaining it omits the trip body, and provides the specific fields returned. The verb 'Get' and resource 'discovery block' are unambiguous.

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?

Explicitly describes when to use: 'Useful for callers that just want who should I meet on this trip?' and contrasts with the full trip endpoint. Provides detailed patterns for the include parameter. Does not state when not to use, but the context is clear enough for an AI agent to choose appropriately.

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