Skip to main content
Glama

vme_start_instance

Starts a stopped HPE VME instance by instance ID, optionally targeting a gateway. The write operation is recorded in the audit log.

Instructions

Start a stopped 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_start_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
instance_idYes

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?

No annotations are supplied, so the description carries the full behavioral burden; it does add real value by disclosing that this is a write operation recorded in the audit log. It does not cover permission requirements, idempotency/behavior on an already-running instance, or what the call returns, leaving meaningful gaps for a mutation tool.

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 core action and the write/audit warning are front-loaded in two short lines, then parameters are listed compactly. The Args block is slightly redundant with the schema's titles but remains lean overall.

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 with no annotations and no output schema, the definition covers the action, the audit implication, and both parameters. It is missing precondition failure behavior, permission/auth needs, and any indication of the response, which an agent would want before invoking a write.

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 compensate, and it does partially: it identifies instance_id as a Morpheus instance ID and marks gateway_id as an optional target gateway. It does not explain gateway selection semantics or how to obtain a gateway ID, so the added meaning is only partial.

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 opens with a precise verb+resource pair ('Start a stopped HPE VME instance') and the state qualifier 'stopped' makes the intent unambiguous against the stop/restart siblings in the catalog. It stops short of explicitly naming those alternatives, so it is clear but not fully differentiated.

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?

The word 'stopped' implies a precondition (the instance must already be halted) and the write/audit note signals this is a state-changing action, which is useful implied guidance. There is no explicit when-to-use vs. vme_restart_instance or vme_stop_instance, and no statement about what happens if the instance is already running.

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