Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

audit_list

Read-only

Retrieve configuration audit records from Nutanix Prism Central, including operation type, user, and creation time, with optional limit and target.

Instructions

[READ] List config audit records (extId, operation type, user, creation time).

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered structurally. The description adds genuinely useful behavior by explaining that results report `returned`, `limit`, and `truncated`, making a capped read visible. However it does not disclose ordering, default newest/oldest, or how to page beyond the limit.

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 record shape, then a compact Args block. Some redundancy between the limit description and its truncation reporting, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers both parameters and the truncation behavior, adequate for a two-param read with no output schema. It stops short of ordering, paging strategy beyond limit, and distinguishing this audit feed from the other event/task list tools in the same namespace.

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 must carry the parameter burden. It documents `limit` (max rows, default 500) and `target` (Prism Central target name, omit for default), adding meaningful semantics that the bare schema lacks, though it could note units or a maximum for limit.

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 config audit records' with the fields returned (extId, operation type, user, creation time). Clearer than a tautology, but does not differentiate itself from the many other *_list siblings (event_list, task_list, alert_list, undo_list).

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?

No statement of when to use this tool versus the sibling list tools such as event_list or task_list. The '[READ]' prefix implies a safe read but gives no routing guidance.

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