Skip to main content
Glama
Sign In
OpManager MCP Server

OpManager MCP Server

by sachdev27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

getVMWareVMs

Lists VMware virtual machines and entities like vCenter, hosts, and datastores for a specified managed entity in OpManager.

Instructions

getVMWareVMs

Category: Manage and query network devices

Key parameters:

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

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "apiKey": "<apiKey>"
    },
    "name": "getVMWareVMs"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesOpManager host address (e.g., 'opmanager.example.com' or 'opmanager.example.com:8061'). Default port is 8061 (HTTPS).
nameNoName 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.
typeNoType of virtual entity which you want to list. (Allowed values: VCENTER , HOST , DATASTORE)
apiKeyYesOpManager API key for authentication

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior1/5

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

The description is incomplete and does not disclose behavior such as what the tool returns, permissions needed, or side effects. Without annotations, the description fails to inform the agent about how the tool behaves.

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

Conciseness1/5

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

The description is extremely short but incomplete, ending mid-sentence. It lacks essential information and does not earn its space.

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

Completeness1/5

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

Given the lack of annotations, output schema, and the complexity of the tool (4 parameters, enums), the description fails to provide necessary context. The truncation makes it unusable for correct invocation.

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

Parameters2/5

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

Although the schema provides 100% coverage, the description adds no additional meaning; it merely repeats parameter names and is truncated. It does not clarify parameter usage or provide context beyond the schema.

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 tool name suggests it lists VMWare VMs, but the description is truncated and the type parameter includes VCENTER, HOST, DATASTORE, creating confusion about whether it lists VMs or other entities. The purpose is not clearly stated.

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 guidance is provided on when to use this tool versus sibling tools like getVMWareDataStores or getVMWareHosts. The description does not specify use cases or exclusions.

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