Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

event_list

Read-only

Lists Nutanix Prism Central events by ID, title, creation time, and source entity, enabling review of system activity and audit trails.

Instructions

[READ] List events (extId, title, creation time, source entity).

Args:
    limit: Max rows to return (default 500). The result reports
        `returned`, `limit`, and `truncated` so a capped read is visible.
    target: Prism Central target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds the meaningful extra that the result reports `returned`, `limit`, and `truncated` so a capped read is visible — real behavioral context an agent would not otherwise know. It still doesn't say anything about ordering, time window, or pagination beyond the cap.

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?

Front-loaded with the read marker and the resource, then a compact Args block with no filler. The docstring-style formatting is slightly verbose but every line carries information.

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?

No output schema exists, yet the description still names the returned fields and explains the truncation reporting, so an agent knows what to expect back. For a two-parameter read-only list tool this is close to complete; only result ordering and default time scope are unstated.

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

Parameters4/5

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

Schema description coverage is 0%, so the description has to carry the load, and it does: it explains `limit` (max rows, default 500, with truncation reporting) and `target` (Prism Central target name from config, omit for default). That is genuinely more than the bare schema types convey.

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?

States a specific verb+resource ("List events") and even enumerates the salient fields returned (extId, title, creation time, source entity). It does not, however, distinguish itself from the many other list tools in the fleet (alert_list, audit_list, task_list, snapshot_list), so an agent gets no explicit routing signal.

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?

There is no statement of when to reach for event_list versus alert_list, audit_list, or task_list, all of which are plausible alternatives for a similar list-shaped call. Usage is only implied by the name and the returned fields.

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