Nutanix AIops

recovery_point_list

Read-only

List recovery points from Nutanix Prism Central, returning extId, VM extId, creation and expiration times, and location type. Set a limit to control results and detect truncation.

Instructions

[READ] List recovery points (extId, vmExtId, create/expiration time, locationType).

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recovery_point_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety needs no restating. The description adds genuine behavioral context beyond the annotations: the 500 default cap and the fact that the result reports `returned`, `limit`, and `truncated` so a capped read is visible. This is exactly the kind of pagination behavior an agent needs.

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] tag and the one-line purpose, then a compact per-argument breakdown. No filler sentences; slightly list-like formatting but every line earns its place.

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?

For a simple two-parameter, no-required-args list tool with no output schema, the description covers both parameters, the return fields, and truncation behavior. An agent has enough to call it correctly; only cross-tool routing guidance is absent.

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 load, and it does: `limit` is documented with its default (500) and truncation semantics, and `target` is explained as a Prism Central target name from config with the omit-for-default rule. This meaningfully exceeds the bare schema types.

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 recovery points') and even enumerates the fields returned (extId, vmExtId, create/expiration time, locationType), making the tool's scope clear. It does not explicitly distinguish itself from the closest sibling, snapshot_list, so it falls short of a 5.

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 when-to-use guidance, no mention of alternatives like snapshot_list, and no conditions for selecting this tool over siblings. The only contextual note ('omit for the default') is about a parameter, not about when the tool is appropriate.

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