Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

announcements_latest

GET /announcements/latest — Latest announcement per channel (quick overview)

Returns the single most recent announcement from each visible channel — a one-shot overview rather than a paged feed. Useful as a "what's new across DC?" quick check before drilling into the full feed via GET /announcements.

Visibility rules are identical to /announcements: DC members see DC-scope channels; DC BLACK members and staff additionally see DC BLACK channels. No pagination — the result size equals the number of dispatch channels you can see (currently ~4).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it is a GET (read-only), returns announcements per visible channel, no pagination, result size equals number of channels (~4), and visibility rules identical to /announcements. No contradictions or omissions.

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 (5 sentences) and well-structured: a header line stating the endpoint and purpose, followed by clear explanations of behavior, usage, visibility, and result size. Every sentence adds value without fluff.

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 the tool's simplicity (no parameters, no output schema), the description is complete. It explains what the tool does, what it returns, visibility rules, pagination behavior, and result size. It also mentions the alternative tool. No gaps remain.

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?

The input schema has zero parameters, so schema coverage is 100% trivially. According to the rubric, zero parameters gives a baseline of 4. The description adds no parameter-specific information, but that is unnecessary; it instead adds context about the output and usage, which is appropriate for a parameterless tool.

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 returns the single most recent announcement per visible channel, using specific verbs ('Returns') and resource description. It distinguishes itself from the sibling 'announcements' tool by explicitly contrasting with the full feed.

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?

The description provides explicit guidance: 'Useful as a quick check before drilling into the full feed via GET /announcements.' It specifies when to use this tool versus the alternative, making context clear.

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