Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

host_list

Read-only

List Nutanix hosts across all clusters, returning extId, cluster, hypervisor, CPU, and memory details. Use limit and target to control results for inventory and capacity checks.

Instructions

[READ] List hosts across all clusters (extId, cluster, hypervisor, CPU/mem).

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

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, but the description adds genuinely new behavior: a default cap of 500 rows and self-reported `returned`/`limit`/`truncated` fields so a truncated read is detectable. That truncation disclosure is real value beyond the annotation, though it doesn't cover auth or per-cluster scoping caveats.

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?

Front-loaded with the READ tag and purpose, then a compact Args block. Every sentence earns its place — no filler, no restatement of the tool name.

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 two-param read with no output schema, the description supplies both parameter semantics and partial return-shape information (the truncation fields vs. the listed entity columns). Nothing critical is missing, though it could clarify whether results are paginated beyond the single cap.

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 defined as max rows with a default of 500 and its effect reflected in the result, and 'target' is explained as a Prism Central target name from config that defaults when omitted. A limit range or upper bound is not given, keeping it just short of a 5.

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?

States a specific verb ('List') and resource ('hosts') with explicit scope ('across all clusters') plus the fields returned (extId, cluster, hypervisor, CPU/mem). No sibling tool overlaps this resource, and the '[READ]' prefix reinforces the operation class, so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb and scope rather than stated: there are no explicit when/when-not rules and no alternatives named. The only routing guidance is the 'target' note (omit for the default), which is parameter-level rather than tool-selection 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