Skip to main content
Glama

vsphere_get_vm_metrics

Retrieve real-time CPU, memory, disk, and network metrics for a vSphere VM to monitor performance and diagnose resource bottlenecks.

Instructions

Get real-time CPU, memory, disk, and network metrics for a vSphere VM.

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": {
      "name": "<name>"
    },
    "name": "vsphere_get_vm_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it discloses very little. It does not say whether the VM must be powered on, what permissions are needed, whether values are instantaneous or averaged, or what the response looks like. 'Real-time' is the only behavioral signal, and its implications (vs. historical sampling) are left unstated.

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?

A single front-loaded sentence with no filler, placing the verb, the metric categories, and the target resource in one pass. It is efficient but borderline under-specified given the tool's two undocumented parameters.

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

Completeness5/5

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

The description gives a clear, specific summary of what data is returned and why an agent would use it for live monitoring, and the two-parameter schema is straightforward. For a simple read-only metrics tool, the definition is sufficient as-is.

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?

Schema description coverage is 0% for two parameters, so the description must compensate — and it only implies that 'name' identifies the VM. The 'gateway_id' parameter is not addressed at all, leaving an agent with no idea when or why to supply it.

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?

The description states a specific verb ('Get') and resource ('real-time CPU, memory, disk, and network metrics for a vSphere VM'), which tells an agent exactly what data comes back. It does not name or contrast with the nearby metric siblings (get_vm_usage, get_gpu_metrics, get_job_metrics), so differentiation is left to the agent's inference.

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 and no mention of alternatives, prerequisites, or exclusions. The word 'real-time' hints at a live-snapshot use case versus historical usage tools, but this is implied rather than stated, and no condition for choosing this tool over get_vm_usage is given.

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