Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

event_schedule_bookmark

POST /events/:eventID/schedule/:sessionID/bookmark — Bookmark / unbookmark a session

Add or remove a session from your personal agenda — this is the API equivalent of the bookmark/star icon on a session card in the DC app.

Requires a valid ticket for the event. Counter rsvpCount on the session doc is updated atomically and idempotently: repeating the same desired state does not increment or decrement the counter again.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIDYesEvent ID
sessionIDYesSession ID
bookmarkedYes`true` to add to agenda, `false` to remove

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It clearly labels the operation as a WRITE (mutates account data), describes idempotent counter updates, and mentions requirements. No contradictions found.

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 concise (few sentences) and well-structured, starting with the endpoint, then the action, then requirements and details. Every sentence adds value with 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?

For a simple toggle without an output schema, the description covers all necessary aspects: purpose, prerequisite, atomic behavior, and mutation warning. It is fully self-contained.

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 parameters are already documented. The description adds context beyond the schema by explaining the bookmark toggle analogy and idempotency, which enhances understanding without being redundant.

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's purpose as 'Bookmark / unbookmark a session' and provides a concrete analogy (bookmark/star icon). It also correctly identifies the HTTP method and resource. While sibling tools like event_rsvp exist, the description distinguishes this as a bookmark toggle without ambiguity.

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?

The description explicitly states the prerequisite ('Requires a valid ticket for the event'), giving a clear condition for when to use. It does not, however, provide direct guidance on when not to use or contrast with alternatives like event_agenda or event_rsvp, leaving some room for inference.

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