Skip to main content
Glama
sachdev27

OpManager MCP Server

by sachdev27

getNutanixDetails

Retrieve details of Nutanix virtual entities such as clusters, hosts, and VMs by specifying the device name and entity type.

Instructions

getNutanixDetails

Category: Manage and query network devices

Key parameters:

  • deviceName: Name of the selected entity type - Managed Entity name as se

  • entityType: Type of virtual entity which you want to list . Allowed valu

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
apiKeyYesOpManager API key for authentication
deviceNameNoName of the selected entity type - Managed Entity name as seen in the URL of device snapshot page OR 'deviceName' property value in the listDevices API response.
entityTypeNoType of virtual entity which you want to list . Allowed values are Nutanix-Cluster , Nutanix-Host , Nutanix-VM
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It does not indicate whether the tool is read-only, requires specific permissions, or has side effects. The incomplete description offers no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but incomplete and cut off. It lacks proper structure and fails to convey essential information in a concise manner.

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

Completeness2/5

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

Given moderate complexity (4 parameters, no output schema), the description is incomplete. It does not explain the return values, behavior, or any additional context needed for effective use.

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

Parameters3/5

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

The input schema has 100% coverage and provides clear descriptions for all four parameters. The description adds minimal extra value, only mentioning two parameters with truncated descriptions. The baseline is 3 since schema covers the parameters well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is vague and truncated. It states a category and lists two key parameters but does not clearly specify that the tool retrieves details for Nutanix clusters, hosts, or VMs. It fails to distinguish from sibling tools like getVMWareVMs or getClusterDetails.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There are no prerequisites, context, or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sachdev27/opmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server