Skip to main content
Glama
Sign In
ntdrive

ntdrive

by jiy2745
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vm_resume

Resume a suspended virtual machine to restore its running state and continue operations.

Instructions

Resume a suspended VM (same as vm_start).

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": {
      "vm": "<vm>"
    },
    "name": "vm_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmYesVM name as registered in vms.yaml

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action (resume) and equivalence to vm_start, but it does not disclose side effects, prerequisites, whether the VM must already be suspended, or what happens if the VM is not suspended. For a state-changing VM operation, this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with a useful parenthetical clarification. Every word earns its place, and the key action is front-loaded.

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 one-parameter tool with full schema coverage, the description is mostly complete. However, it lacks behavioral context such as whether the VM must be in a suspended state, whether the operation is asynchronous, or what errors might occur. The equivalence to vm_start helps, but the description could do more to make the tool safely invocable.

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 100%, so the schema already documents the single 'vm' parameter as 'VM name as registered in vms.yaml'. The description adds no additional parameter meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource: 'Resume a suspended VM', and it explicitly equates the behavior with vm_start, which helps distinguish it from other VM lifecycle tools. It is clear but relies on the parenthetical to differentiate it from vm_start rather than fully standing alone.

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 description implies the tool is for resuming a suspended VM, which gives clear context for when to use it. It does not explicitly state when not to use it or name alternatives beyond the parenthetical equivalence to vm_start, so usage guidance is adequate but not fully explicit.

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