Skip to main content
Glama

vme_get_instance

Get detailed status and configuration for a specific HPE VME instance, including CPU, memory, disk, network, cloud assignment, service plan, creation date, and IP address.

Instructions

Get detailed status and configuration of a specific HPE VME instance.

Returns CPU, memory, disk, network, cloud assignment, service plan, creation date and IP address.

Args: instance_id: Morpheus instance ID (from vme_list_instances). 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_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and the verb 'Get' plus the enumerated read-out fields make the read-only, non-destructive nature clear. It does not disclose authentication/permission needs, what happens if the instance ID is invalid or the instance is in a transitional state, or what the optional gateway actually changes about the request.

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 purpose and return contents are front-loaded in two tight sentences, and the parameter block is short. The 'Args:' block partly restates names already visible in the schema, but the added sourcing note for instance_id earns its place; nothing is padded.

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?

There is no output schema, so the description's enumeration of returned fields is genuinely load-bearing and sufficient for the return side. However, for a status-inspection tool with a vague optional parameter and no annotation coverage, it omits error/failure behavior and the semantics of gateway_id, leaving gaps an agent could hit in edge cases.

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 coverage is 0%, so the schema provides no parameter descriptions and the description must compensate. It explains instance_id well (Morpheus instance ID, sourced from vme_list_instances) but gateway_id is only 'Target gateway (optional)' — no format, valid values, or effect on the result — leaving one of two parameters effectively undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition opens with a specific verb+resource ('Get detailed status and configuration of a specific HPE VME instance') and the word 'specific' implicitly separates it from the listing sibling vme_list_instances. It then enumerates the exact fields returned (CPU, memory, disk, network, cloud assignment, service plan, creation date, IP address), so an agent knows precisely what it is asking for.

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?

Usage is only implied: the note that instance_id comes 'from vme_list_instances' sketches a two-step workflow, which is a helpful hint. There is no explicit statement of when to use this versus vme_get_activity or the list tool, no prerequisites, and no exclusions, so the agent must infer the selection criteria.

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