Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

calendar_update

PATCH /calendar — Update calendar feed settings

Update any subset of your calendar feed toggles. Send only the toggles you want to change — omitted fields are left untouched. Returns { updated: true } on success; re-fetch GET /calendar if you need the full toggle set + feed URLs (the URLs themselves are stable and don't change when toggles update).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeMyTripsNoBoolean
includeMyTicketsNoBoolean
includeEventAgendaNoBoolean
includeVirtualCallsNoBoolean
includeDCBlackEventsNoBoolean
includeFlagshipEventsNoBoolean
includeHomeChapterEventsNoBoolean
includeOtherChapterEventsNoBoolean
includeFollowedChapterEventsNoBoolean

TDQS

A4.5/5.0
Behavior5/5

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

Explicitly declares this is a WRITE operation that mutates DC account data. Describes return value and behavior on success. No annotations provided, so description fully compensates.

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?

Three focused sentences: purpose, usage nuance, and side-effect/return info. No filler, front-loaded with key information.

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 tool with 9 simple boolean parameters and no output schema, description covers behavior (partial update, return value, side-effect), and provides complete context for agent invocation.

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?

Schema coverage is 100% with each parameter described as 'Boolean'. Description adds general context about partial updates but does not provide additional meaning per parameter beyond the 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?

Clearly states 'Update calendar feed settings' with specific verb and resource, and specifies 'any subset of your calendar feed toggles'. Distinguishes from sibling tools like 'calendar' which is a GET endpoint.

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?

Provides clear guidance: send only toggles to change, omitted fields left untouched, and suggests re-fetching GET /calendar for full state. Lacks explicit when-not-to-use or comparison with alternative update tools, but context is sufficient.

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