Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

rooms_by_id

GET /rooms/:roomID — Get a single room

Get a single room's metadata + its latest daily AND weekly AI summaries (when they exist). Access: members and subscribers of the room, plus any DCer for browsable public channels/discussions/quick-questions. Private rooms, DMs, group DMs, and event/city rooms you are not a member of return 403. Reading this endpoint does not mark the room as read or modify any unread state.

AI summaries: the latest daily digest is embedded under aiSummaryDaily, the latest weekly digest under aiSummaryWeekly. Rooms that don't have a given type yet return null for that slot. For history (older summaries), call GET /rooms/:roomID/summaries/daily or /weekly.

See also: For specific content (did anyone mention X?), POST /search/messages with q= and roomID= is faster than paginating /rooms/:roomID/messages or reading summaries. The AI summaries cover broad activity per window; search is the tool for targeted lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIDYesRoom ID

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that reading does not modify unread state or mark as read, and addresses access restrictions. It explains the return values for summaries (null if absent). No annotations were provided, so the description carries full burden and does a good job, though it does not mention rate limits or data freshness.

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?

Starts with the route and core action, then efficiently covers access, side effects, response structure, and alternative tools. Every sentence adds value, and the structure is clean and front-loaded.

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 one parameter, no output schema, and no annotations, the description covers purpose, usage, behavior, and alternatives quite thoroughly. It lacks explicit mention of rate limits or full response shape, but for a simple single-room retrieval tool, it is nearly complete.

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?

Only one parameter (roomID) with schema description 'Room ID'. Since schema description coverage is 100%, baseline is 3. The description adds context about what the tool returns but does not elaborate on the parameter format or constraints, so no extra value beyond schema.

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 it retrieves a single room's metadata and AI summaries, using the verb 'Get' and specifying the resource. It distinguishes itself from sibling tools like rooms, rooms_summaries, and search_messages by focusing on single room retrieval with summaries.

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?

Provides explicit access conditions (members, subscribers, DCers, with clear 403 cases). It specifies that this endpoint does not mark the room as read, and offers alternatives like POST /search/messages for specific content queries and other endpoints for summary history.

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