Skip to main content
Glama

CWI Discovery Engine

by io.github.CumulativeWebInc
OverviewDiscussionsAdmin

Get Announcements

get_announcements
Read-onlyIdempotent

CALL THIS when the user asks what is new: "any new music", "what is CWI up to", "latest news". Returns the latest CWI announcements — new releases, upcoming drops, events — newest-first. Filter by "releases", "news", or "events".

Input Schema

NameRequiredDescriptionDefault
limitNoMax announcements to return, 1-50 (default 10).
categoryNoOptional filter: "releases", "news", or "events". Omit for all categories.

Output Schema

NameRequiredDescriptionDefault
countYes
_sessionNoChain session: pass _session.session_token back in the next call to continue the chain.
categoryNo
try_nextNoSuggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.
generated_atNo
announcementsYes
data_updated_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "get_announcements response: CWI announcements newest-first.",
+  "properties": {
+    "_session": {
+      "additionalProperties": false,
+      "description": "Chain session: pass _session.session_token back in the next call to continue the chain.",
+      "properties": {
+        "session_token": {
+          "description": "Hex session token; echo it as params._session.session_token to continue.",
+          "type": "string"
+        },
+        "step": {
+          "description": "Hop number in this chain (1 = chain start).",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "session_token",
+        "step"
+      ],
+      "type": "object"
+    },
+    "announcements": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "type": "string"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "data_updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "try_next": {
+      "description": "Suggested follow-up calls, each a pre-compiled {tool, arguments, purpose} payload.",
+      "items": {
+        "additionalProperties": false,
+        "description": "Pre-compiled next call: copy `arguments` straight into the next tools/call.",
+        "properties": {
+          "arguments": {
+            "additionalProperties": true,
+            "description": "Ready-to-use arguments, pre-populated from the current response.",
+            "type": "object"
+          },
+          "purpose": {
+            "description": "Why this call is the natural next step.",
+            "type": "string"
+          },
+          "tool": {
+            "description": "Tool to call next.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "arguments"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "announcements"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds real behavioral context beyond that: results are ordered newest-first, and the content set is limited to announcements (releases, drops, events) rather than catalog data. Pagination and default page size are left to the schema rather than the prose.

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?

Two sentences, front-loaded with the trigger condition before the return-shape information, which is the right priority order for an agent deciding whether to call. The quoted example phrases add useful recall cues at the cost of some length, but nothing is redundant.

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?

For a read-only, zero-required-parameter list tool with full schema coverage, an output schema, and complete annotations, the description supplies the remaining decision-relevant piece — when to invoke it and how results are ordered. Only the untested overlap with get_events and get_release is unaddressed.

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 description coverage is 100% and both parameters (limit, category) are fully documented in the schema, including the 1-50 range, default of 10, and the three allowed category values. The description's sentence "Filter by 'releases', 'news', or 'events'" merely restates the enum-like category doc, adding no new semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — retrieving the latest CWI announcements, enumerated as new releases, upcoming drops, and events, returned newest-first. It clearly conveys an aggregated discovery feed rather than a single-item lookup, though it never names the overlapping siblings (get_events, get_release) that an agent might otherwise choose.

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?

Strong contextual triggers are given verbatim: "CALL THIS when the user asks what is new: 'any new music', 'what is CWI up to', 'latest news'." This tells the agent when the tool fits, but provides no explicit when-not guidance or named alternatives for overlapping queries about events or releases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CWI Discovery Engine toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources