Skip to main content
Glama
AIops-tools

io.github.AIops-tools/olvm-aiops

Official
by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

event_list

Retrieve engine events filtered by severity and recency, with pagination and incremental fetch for new events.

Instructions

[READ] Engine events at or above a severity, newest first.

To follow new events, pass the highest index you have already seen as after_index: events after it come back OLDEST first (order), so repeat with the highest index returned while truncated is true and nothing is skipped. since_minutes keeps events from the last N minutes and sets scanTruncated when older ones in the window may be missing. SSO session ids in login events are redacted.

Args: limit: Rows to return, 1-1000 (default 100); truncated says when more exist. min_severity: One of normal, warning, error, alert (default normal). page: Older pages of events (not combinable with since_minutes or after_index). after_index: Only events with a higher index than this, oldest first. since_minutes: Only events from the last N minutes (1-129600). target: Engine target name from config; omit to use the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
targetNo
after_indexNo
min_severityNonormal
since_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses ordering inversion when using after_index, truncation semantics, scanTruncated caveats, and redaction of SSO session IDs. The [READ] marker also signals non-mutating behavior.

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?

The description is dense but well organized: a one-line purpose, a short usage paragraph for the non-obvious cursor behavior, then a terse Args list. Every sentence adds needed operational detail without filler.

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?

Despite having no output schema and no annotations, the description is complete enough for an agent to call the tool correctly. It defines all parameters, explains repeated-call pagination semantics, and warns about missing events and redacted fields.

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?

Schema description coverage is 0%, so the description must explain every parameter, and it does. The Args block covers all six parameters with ranges, defaults, enum values, and combinability constraints such as page not being combinable with since_minutes or after_index.

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 identifies the operation as reading engine events, the resource involved, and the key filtering/ordering behavior: severity threshold and newest-first ordering. This distinguishes it from the sibling tools, none of which list engine events.

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 concrete usage guidance for following new events with after_index, using since_minutes for recent events, and using page for older pages, including an explicit incompatibility between page and the other modes. It does not name alternative tools, but the provided context is sufficient given the sibling list.

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