Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

rooms_subscribe_create

POST /rooms/:roomID/subscribe — Subscribe to a room

Subscribe to a public channel, discussion, quick-question room, or event room. The caller is added to the room's seen subcollection with flags.isSubscribed: true and starts receiving its updates in their inbox.

Access: the room must be enabled, non-archived, non-private, non-hidden, and of a subscribable type (channel, discussion, quick-question, event). Event rooms additionally require a valid ticket to the linked event — call /events/:eventID first to verify ticket status. DMs and group DMs cannot be subscribed/unsubscribed via the API; they are managed in-app only.

Idempotent: subscribing when already subscribed is a no-op (returns 200 with the current state).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIDYesRoom ID

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that this is a WRITE operation, idempotent, and describes access conditions (room must be non-archived, non-private, etc.). Adds detail about the internal effect (flags.isSubscribed: true). Could mention error responses, but given no output schema, this is adequate.

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?

Well-structured with bold headings for Access and Idempotent. Concise enough given the necessary detail; no superfluous sentences. A bit verbose but still effective.

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 required parameter and no output schema, the description covers purpose, access conditions, idempotency, and mutation warning. Lacks details on error scenarios or exact response format, but is sufficient for a simple subscribe action.

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% (roomID with description 'Room ID'). Description adds semantic context: roomID must belong to a subscribable type and event rooms require a valid ticket. This adds value beyond the schema's basic type info.

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 the verb 'subscribe' and resource 'room', specifies subscribable room types (channel, discussion, quick-question, event), and distinguishes from siblings like rooms_unsubscribe_create. The description is specific about the effect (added to seen subcollection).

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 states when to use (subscribable room types) and when not (DMs/group DMs must be managed in-app). Includes prerequisites for event rooms (valid ticket). Does not directly name alternatives but provides clear context for correct usage.

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