Opencollective

Events

events

Read-onlyIdempotent

Events for a collective.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of items returned.
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "slug": "babel"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "attendees": {
+            "description": "Number of attendees",
+            "type": "number"
+          },
+          "description": {
+            "description": "Event description",
+            "type": "string"
+          },
+          "endsAt": {
+            "description": "Event end date (ISO 8601)",
+            "type": "string"
+          },
+          "id": {
+            "description": "Event ID",
+            "type": "string"
+          },
+          "image": {
+            "description": "Event image URL",
+            "type": "string"
+          },
+          "location": {
+            "description": "Event location",
+            "type": "string"
+          },
+          "name": {
+            "description": "Event name",
+            "type": "string"
+          },
+          "slug": {
+            "description": "Event slug",
+            "type": "string"
+          },
+          "startsAt": {
+            "description": "Event start date (ISO 8601)",
+            "type": "string"
+          },
+          "timezone": {
+            "description": "Event timezone",
+            "type": "string"
+          },
+          "url": {
+            "description": "Event page URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds no behavioral context beyond what annotations provide, such as scope of results or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (3 words) but fails to convey essential information. Conciseness is positive only when it retains utility; here it is under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (not shown), the description gives no sense of what events are returned, whether there are limitations, or how this tool fits with others. Incomplete for a simple tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only says 'Events for a collective.' It does not explain the 'slug' parameter's meaning, format, or how it relates to the output. The schema example ('babel') offers minimal help.

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

Purpose2/5

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

The description 'Events for a collective.' is vague and lacks a verb. It does not specify whether the tool retrieves, lists, or manages events. Among siblings, 'collective' hints at a relation but no clear action is stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'collective', 'transactions'), the description provides no context to differentiate or indicate prerequisites.

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

All Opencollective tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.