Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

trips

GET /trips — List your trips

Returns your upcoming trips by default. Add ?past=true to include past trips.

For "who should I meet on this trip?" fetch GET /trips/:tripID (or the discovery-only GET /trips/:tripID/discovery) — both return the ranked top-10 DCers + AI-written summaries + the full pool of locals and visitors in town during the trip window. The list response below does NOT include the discovery block (lazy by design — discovery is a much heavier payload).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pastNoInclude past trips.
limitNoMax results (1-100).
cursorNoCursor from a previous response's `nextCursor`. Pass to fetch the next page.

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the operation is a GET (read-only), that it excludes the heavy discovery block for efficiency, and implies pagination via cursor. It does not contradict any annotations (none exist).

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?

The description is three sentences, well-structured, and front-loaded with the primary purpose. It uses bold to highlight the alternative endpoint, and every sentence adds value. No wasted words.

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 absence of an output schema, the description sufficiently covers the list endpoint's behavior: default scope, pagination via cursor, and the critical distinction from detail endpoints. It explains why discovery is omitted, which is important context. The 3 parameters are all addressed.

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 that the 'past' parameter defaults to false and that '?past=true' is needed to include past trips. While limit and cursor are not elaborated beyond schema, this slight addition warrants a 4.

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 trips via 'GET /trips — List your trips'. It specifies the default behavior (upcoming trips) and differentiates from sibling tools by noting that the detail endpoints (e.g., GET /trips/:tripID) include discovery information, while this list response does not.

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?

The description provides explicit guidance: use ?past=true for past trips, and for discovery-related queries (who to meet), use the detail endpoints. It also notes the lazy design choice to avoid heavy payloads, helping the agent decide when to use this tool versus trip_discovery.

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