server

CYCLOID_EVENT_LIST

Read-only

List organization events with optional filters. To filter by WHAT HAPPENED, use action (e.g. create, update, delete, configure, pause, unpause) and/or entity (e.g. component, ci_build, ci_job, pipeline, credential) — these are matched case-insensitively against each event's actual action/entity tag VALUE (note: the entity is ci_build, not build). If a filter matches nothing while events exist, the response lists the available_actions/available_entities to retry with. type is ONLY the high-level category: Cycloid, AWS, Monitoring, Custom (do NOT pass an action/entity name as type). severity is one of: info, warn, err, crit. begin/end are Unix timestamps in SECONDS (strings); omit any filter to include all of its values. Returns full event payload including tags. Actor identity is in tags as {key: 'user', value: ''}.

Input Schema

Name	Required	Description
`end`	No	Unix timestamp (string) end date.
`type`	No	Event categories to include (Cycloid, AWS, Monitoring, Custom).
`begin`	No	Unix timestamp (string) start date.
`action`	No	Filter by the event's `action` tag (e.g. create, configure, pause).
`entity`	No	Filter by the event's `entity` tag (e.g. component, ci_build, pipeline).
`severity`	No	Event severities to include (info, warn, err, crit).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / action

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by the event's `action` tag (e.g. create, configure, pause)."
+}

addedInput schema / properties / begin / description

Added value: +"Unix timestamp (string) start date."

addedInput schema / properties / end / description

Added value: +"Unix timestamp (string) end date."

addedInput schema / properties / entity

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by the event's `entity` tag (e.g. component, ci_build, pipeline)."
+}

removedInput schema / properties / format

Removed value: -{
-  "default": "json",
-  "type": "string"
-}

changedInput schema / properties / severity / anyOf

Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "enum": [
+        "info",
+        "warn",
+        "err",
+        "crit"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / severity / description

Added value: +"Event severities to include (info, warn, err, crit)."

changedInput schema / properties / type / anyOf

Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "enum": [
+        "Cycloid",
+        "AWS",
+        "Monitoring",
+        "Custom"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / type / description

Added value: +"Event categories to include (Cycloid, AWS, Monitoring, Custom)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond readOnlyHint, the description discloses important behavior: filters are case-insensitive against tag values, entity names use ci_build rather than build, unmatched filters return available_actions/available_entities for retry, and full event payloads including tags are returned. It also identifies actor identity via the user tag. This is substantial behavioral context beyond the annotations.

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?

The purpose is front-loaded and every sentence carries useful information, including edge-case behavior and parameter constraints. The description is a dense paragraph rather than structured bullets, which slightly reduces scannability for a six-parameter tool.

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?

The definition is complete for an optional-filter list tool: it covers scope, filter semantics, fallback behavior, timestamp format, return payload, and actor identification. An output schema exists, and the annotations cover the read-only safety profile, so no critical context appears missing.

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

Parameters5/5

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

Although schema coverage is already 100%, the description adds meaning that the schema does not: action/entity match actual tag values case-insensitively, type must not receive action/entity names, begin/end are Unix timestamps in seconds as strings, and omitting a filter includes all its values. These clarifications materially improve correct parameter use.

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: 'List organization events with optional filters.' The organization scope implies a distinction from project-level siblings, but the description does not explicitly call out CYCLOID_PROJECT_EVENTS or any other alternative. Purpose is clear, but sibling differentiation is left implicit.

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 gives clear context for using filters, including how action/entity matching works, that type is a high-level category, and that omitted filters include all values. It does not explicitly state when to use this tool instead of CYCLOID_PROJECT_EVENTS, so alternatives are not covered.

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

All server tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.