Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

event_list

List recent system events and filter them by type, source, entity, or project. Use compact rows by default or request full payloads with fields=all.

Instructions

List recent events in the system, optionally filtered.

Default response is a COMPACT projection (marked by view="compact" + hint — it is a trimmed view, NOT missing fields): each row keeps id/type/source/ts plus a one-line summary derived from the event payload. Use fields="all" for full payloads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoExact event type, e.g. "task.completed" / "agent.created"
limitNoMaximum number of events to return, default 50 (compact view caps the window at 60 rows; fields="all" is uncapped)
fieldsNo"compact" (default, trimmed projection) / "all" (full rows)compact
sourceNoExact event source, e.g. "team:<id>" / "agent:<id>" / "repository"
entity_idNoFilter to one entity (task / agent / meeting id)
project_idNoScope to a project — resolves to that project's teams and returns their team/agent/task events (empty = no project scoping; pass "auto" to use the active project)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.11.2
    • addedInput schema / properties / entity_id
      Added value: +{
+  "default": "",
+  "description": "Filter to one entity (task / agent / meeting id)",
+  "type": "string"
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default, trimmed projection) / \"all\" (full rows)",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of events to return, default 50"New value: +"Maximum number of events to return, default 50 (compact view\ncaps the window at 60 rows; fields=\"all\" is uncapped)"
    • addedInput schema / properties / project_id
      Added value: +{
+  "default": "",
+  "description": "Scope to a project — resolves to that project's teams and\nreturns their team/agent/task events (empty = no project scoping;\npass \"auto\" to use the active project)",
+  "type": "string"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "default": "",
+  "description": "Exact event source, e.g. \"team:<id>\" / \"agent:<id>\" / \"repository\"",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "default": "",
+  "description": "Exact event type, e.g. \"task.completed\" / \"agent.created\"",
+  "type": "string"
+}
  2. First observedv1.9.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does meaningfully warn that the default result is a trimmed projection (id/type/source/ts + summary) marked by view="compact" + hint, explicitly pre-empting the 'are fields missing?' misread, and notes the 60-row compact cap. It stops short of stating auth/permission requirements or ordering guarantees.

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 tight sentences, front-loaded with the core action and then the non-obvious default-view caveat. The parentheticals are dense but each carries real information; nothing is padding.

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?

An output schema exists so return values need not be described, and the description covers the one genuinely surprising behavior (default compact projection). What is missing is the 'recent' ordering/window semantics and any note on result limits for the compact path beyond the 60-row hint.

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%, so the schema already documents all six parameters including the compact/all distinction and the limit cap. The description reinforces the compact-vs-all semantics but adds no format or syntax detail beyond what the schema provides, 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 gives a specific verb and resource ('List recent events in the system') plus its scoping ('optionally filtered'), which is clear enough for an agent to act on. It does not, however, differentiate itself from near-neighbors such as agent_activity_query or ecosystem_repo_events, so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: the agent learns it can filter and can switch to fields="all", but nothing states when to reach for this tool over the many sibling listing/query tools. No when-not or alternative routing is offered.

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

Deploy Server

Other Tools