Skip to main content
Glama

vme_detect_vm_waste

Identify stopped and over-provisioned VMs in HPE VME, then return severity-ranked recommendations for FinOps reviews and cost optimisation.

Instructions

Detect VM waste in HPE VME: stopped instances and over-provisioned VMs.

Returns actionable recommendations with severity levels. Use for FinOps reviews and cost optimisation.

Args: stopped_days_threshold: Flag VMs stopped for more than N days (default: 7). gateway_id: Target gateway (optional).

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": "vme_detect_vm_waste"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
stopped_days_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the burden: 'Detect' implies a read-only analysis, and it discloses that output includes actionable recommendations with severity levels, which is genuinely useful. It does not state permission requirements, whether it scans all gateways or one, or how 'over-provisioned' is determined.

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?

Purpose and return information are front-loaded in two short sentences, followed by a compact Args block. There is no filler, though the Args section largely restates schema titles.

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

Completeness3/5

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

For a two-optional-parameter tool with no annotations and no output schema, the description covers purpose, use case, return contents, and both parameters. It leaves a real gap: 'over-provisioned VMs' is promised but no parameter or explanation indicates how that condition is detected or tuned.

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?

Schema description coverage is 0%, so the description is the only source for parameter meaning, and it does cover both: stopped_days_threshold as a day-count threshold for flagging stopped VMs, and gateway_id as an optional target. Both explanations are shallow — no expected format for gateway_id (ID vs name) and no interaction between the parameters.

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 gives a specific verb+resource ('Detect VM waste in HPE VME') and names the two waste categories it covers: stopped instances and over-provisioned VMs. It is clear on its own, though it never references the sibling 'get_waste_analysis' to disambiguate the two analysis tools.

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?

'Use for FinOps reviews and cost optimisation' implies the scenario but gives no explicit when-not conditions and no alternatives. It does not tell the agent whether to prefer this over get_waste_analysis or the per-VM tools like vme_get_instance.

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