Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

rooms_unsubscribe_create

POST /rooms/:roomID/unsubscribe — Unsubscribe from a room

Unsubscribe from a public channel, discussion, quick-question, or event room. The caller's seen doc is updated to flags.isSubscribed: false, the badge count is cleared, and the room drops out of the inbox sidebar.

Access: the caller must already be a subscriber. DMs and group DMs cannot be unsubscribed via the API.

Idempotent: unsubscribing when already unsubscribed is a no-op.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIDYesRoom ID

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses effects: updates `seen` doc, clears badge count, removes from inbox. Explicitly marks as a WRITE operation with a warning about data mutation.

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?

Concise yet comprehensive: single line for endpoint/purpose, bullet points for access, idempotency, and warning. No fluff, every sentence adds value.

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 simple input schema, no output schema, and no annotations, the description fully covers the action, access constraints, idempotency, and mutation details, making it complete for an agent to use.

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'. The description adds no further meaning beyond the schema, which already has 100% coverage. Baseline score of 3 is appropriate.

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 explicitly states the tool unsubscribes from a room, listing the room types (public channel, discussion, quick-question, event). It distinguishes from siblings like rooms_subscribe_create (subscribe) and other room management tools.

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?

Clearly specifies when to use (caller must already be a subscriber) and when not to use (DMs and group DMs cannot be unsubscribed). Also mentions idempotency, providing guidance on repeated calls.

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