Skip to main content
Glama
anyvm-org

anyvm-mcp

Official
by anyvm-org
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

start_vm

Boot a guest VM in the background and return SSH connection details. Configure OS, release, CPU, memory, ports, volumes, and snapshot mode.

Instructions

Boot a guest VM in the background. The first boot of an OS/release downloads the image (hundreds of MB -- allow several minutes). Returns SSH connection details on success. OS and release are separate: os='freebsd' release='14.3', not 'freebsd-14.3'. Omit release to get the default release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osYes
archNo
cpusNo
syncNo
portsNo
mem_mbNo
releaseNo
volumesNo
snapshot_modeNo
boot_timeout_secNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed13 schema fields changedv0.0.3
    • addedInput schema / properties / arch
      Added value: +{
+  "default": "",
+  "title": "Arch",
+  "type": "string"
+}
    • addedInput schema / properties / boot_timeout_sec
      Added value: +{
+  "default": 1800,
+  "title": "Boot Timeout Sec",
+  "type": "integer"
+}
    • addedInput schema / properties / cpus
      Added value: +{
+  "default": 0,
+  "title": "Cpus",
+  "type": "integer"
+}
    • addedInput schema / properties / mem_mb
      Added value: +{
+  "default": 0,
+  "title": "Mem Mb",
+  "type": "integer"
+}
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • addedInput schema / properties / os
      Added value: +{
+  "title": "Os",
+  "type": "string"
+}
    • addedInput schema / properties / ports
      Added value: +{
+  "default": [],
+  "items": {
+    "type": "string"
+  },
+  "title": "Ports",
+  "type": "array"
+}
    • addedInput schema / properties / release
      Added value: +{
+  "default": "",
+  "title": "Release",
+  "type": "string"
+}
    • addedInput schema / properties / snapshot_mode
      Added value: +{
+  "default": false,
+  "title": "Snapshot Mode",
+  "type": "boolean"
+}
    • addedInput schema / properties / sync
      Added value: +{
+  "default": "",
+  "title": "Sync",
+  "type": "string"
+}
    • addedInput schema / properties / volumes
      Added value: +{
+  "default": [],
+  "items": {
+    "type": "string"
+  },
+  "title": "Volumes",
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "os"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "start_vmOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description covers that booting happens in the background, returns SSH details, and first boot is slow. It lacks disclosure on potential conflicts, resource limits, or state changes beyond creation. Adequate but not comprehensive.

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?

Three sentences, each adding distinct value: purpose, performance caveat, and parameter clarification. No redundant or vague statements; information is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, no output schema, no annotations), the description is too sparse. Key details about optional parameters and expected return values beyond SSH info are missing, making it incomplete for an agent to use effectively.

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. It only explains two parameters (os and release) with formatting hints, leaving eight parameters (arch, cpus, ports, etc.) completely unexplained. This is insufficient for a tool with 10 parameters.

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 description clearly states the tool boots a guest VM in the background, specifying the action and resource. It distinguishes from sibling tools like list_supported_os or exec_in_vm by focusing on VM startup and return of SSH details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on first boot performance and the correct format for os and release parameters, including how to get the default release. However, it does not discuss when alternatives might be preferred or when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/anyvm-org/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server