Skip to main content
Glama
Mustafa-Ali-Ertugrul

AllBrain MCP

by Mustafa-Ali-Ertugrul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_events

Query and filter recorded events from the append-only event log to inspect the history of agent actions and system state changes.

Instructions

Query and filter recorded events from the append-only event log.

Use this to inspect the history of agent actions and system state changes. Events are ordered by stable UUIDv7 timestamps for consistent replay.

Side effects: Read-only operation; no data is modified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional event type to filter by (e.g., "TASK_CREATED", "TASK_ASSIGNED", "TOOL_CALLED").
limitNoMaximum number of events to return (default 50). Increase for broader history inspection.
session_idNoOptional session ID to filter by (useful for multi-agent debugging and isolation).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • removedInput schema / properties / agent_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return (default 50). Increase for\nbroader history inspection."
    • removedInput schema / properties / project_path
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • addedInput schema / properties / session_id / description
      Added value: +"Optional session ID to filter by (useful for multi-agent\ndebugging and isolation)."
    • addedInput schema / properties / type / description
      Added value: +"Optional event type to filter by (e.g., \"TASK_CREATED\",\n\"TASK_ASSIGNED\", \"TOOL_CALLED\")."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Explicitly declares read-only nature and mentions ordering by UUIDv7 timestamps for consistent replay, providing good behavioral context beyond the absence of annotations.

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?

Three concise sentences front-loaded with the purpose, followed by usage and side effects, with no wasted words.

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?

Covers purpose, usage, ordering, and side effects; with an output schema present, it need not explain return values, making it complete for this tool.

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 coverage is 100%, so the baseline is 3; the description does not add new meaning to parameters beyond what the schema already provides.

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 the tool queries and filters events from an append-only event log, distinguishing it from siblings like save_event or summarize_sessions.

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?

It advises using the tool to inspect history of agent actions and system state changes, but does not explicitly state when to avoid it or mention alternatives beyond implicit context.

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