Skip to main content
Glama

vme_restart_instance

Restart an HPE VME instance using its Morpheus instance ID to recover from issues; optionally specify a gateway for the restart.

Instructions

Restart an HPE VME instance.

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_restart_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does add one genuinely useful fact — 'Write operation — recorded in the audit log' — which discloses mutation and auditability. However it says nothing about disruptiveness/downtime, whether the call blocks until restart completes, idempotency, or required permissions, which are the traits an agent most needs for a restart.

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?

Front-loaded with the action and the audit note; the Args block is terse. Minor waste: 'write operation' is partly implied by 'Restart', and the Args entries largely restate the schema titles rather than adding content.

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-parameter mutation tool with no annotations and no output schema, the definition covers the action and its auditability but leaves the gateway parameter's purpose and the call's return/blocking behavior undefined. Adequate minimum, with clear gaps.

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%, so the description must compensate for both parameters. It clarifies instance_id as a 'Morpheus instance ID' (mild help, and it implies integer vs UUID) but describes gateway_id only as 'Target gateway (optional)' — a restatement of the schema's null default with no explanation of what routing through a gateway changes or when to supply one.

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: 'Restart an HPE VME instance.' That is enough to distinguish it from the vme_start_instance / vme_stop_instance siblings by action alone, but the description never names those alternatives, so differentiation is left partly to the reader.

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 guidance on when to restart versus stop-then-start, no precondition state (e.g. instance must exist and not already be restarting), and no exclusions. The only usage signal is the implicit semantics of the verb.

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