Skip to main content
Glama

vme_stop_instance

Stops a running HPE VME instance with a graceful shutdown and records the action in the audit log; optionally targets a specific gateway.

Instructions

Stop a running HPE VME instance (graceful shutdown).

Write operation — recorded in the audit log.

Args: instance_id: Morpheus instance ID. gateway_id: Target gateway (optional).

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

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does useful work by flagging this as a write operation recorded in the audit log and by specifying graceful (rather than forced) shutdown. It omits what happens if the instance is already stopped, whether the action is reversible, permission requirements, and whether the call is synchronous.

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?

The operational sentence is front-loaded and the audit-log note is a single efficient clause. The Args block largely restates schema titles, making it the only mildly redundant element.

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 simple two-parameter mutation with no annotations and no output schema, the definition covers identity and intent but leaves preconditions, failure modes, and result behavior unstated. Adequate to call, not fully complete.

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 must carry parameter meaning. It identifies both parameters and marks gateway_id as optional, but 'Morpheus instance ID' and 'Target gateway' add little beyond the schema's own titles and give no format, source, or lookup guidance.

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?

States a specific verb+resource ('Stop a running HPE VME instance') with the mode of operation ('graceful shutdown'), which distinguishes it from vme_restart_instance and vme_start_instance by implication. It stops short of naming a sibling explicitly, so it sits just below the top band.

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 explicit guidance on when to use this versus vme_restart_instance or a forced/terminate path, and no stated prerequisites (e.g., instance must be running). Usage is only inferable from the tool name and the word 'stop'.

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