Skip to main content
Glama
ycyun

ABLESTACK MOLD MCP Server

by ycyun

VM 시작

mold_startVirtualMachine

Start a virtual machine in ABLESTACK MOLD to launch cloud instances, supporting optional parameters for host, cluster, pod selection, boot setup, and last host consideration.

Instructions

startVirtualMachine(4.21). 반환에 jobid가 포함될 수 있음(비동기).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
hostidNo
clusteridNo
podidNo
considerlasthostNo
bootintosetupNo

Implementation Reference

  • Registration of the 'mold_startVirtualMachine' MCP tool, including input schema and handler function that delegates to the underlying MOLD 'startVirtualMachine' API via callApi.
    server.registerTool(
      "mold_startVirtualMachine",
      {
        title: "VM 시작",
        description: "startVirtualMachine(4.21). 반환에 jobid가 포함될 수 있음(비동기).",
        inputSchema: {
          id: z.string(),
          hostid: z.string().optional(),
          clusterid: z.string().optional(),
          podid: z.string().optional(),
          considerlasthost: z.boolean().optional(),
          bootintosetup: z.boolean().optional(),
        },
      },
      async (args) => {
        const data = await callApi("startVirtualMachine", args);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the return may include a jobid (asynchronous), which is useful context about the operation's nature. However, it doesn't cover critical aspects like required permissions, whether this is a destructive operation, rate limits, or error conditions. The description adds some value but leaves significant gaps.

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 description is very concise with just one sentence containing two clauses. It's front-loaded with the tool name and includes relevant behavioral information about asynchronous returns. There's no wasted text, though it could benefit from slightly more detail given the complexity of the tool.

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?

For a tool with 6 parameters (0% schema coverage), no annotations, no output schema, and complex VM operations, the description is inadequate. It mentions the asynchronous nature but doesn't explain parameter meanings, required permissions, side effects, or how to handle the jobid return. The description doesn't provide enough context for safe and effective use.

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 completely undocumented parameters. The description provides no information about any of the 6 parameters (id, hostid, clusterid, podid, considerlasthost, bootintosetup). It doesn't explain what these parameters mean, their relationships, or which are required versus optional beyond what the schema already indicates.

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

Purpose3/5

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

The description states 'startVirtualMachine' which clearly indicates the verb (start) and resource (Virtual Machine), but it doesn't specify what distinguishes it from sibling tools like 'mold_stopVirtualMachine' or 'mold_listVirtualMachines'. The version number '(4.21)' adds some specificity but doesn't clarify functional differentiation.

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?

No guidance is provided about when to use this tool versus alternatives. There's no mention of prerequisites, when not to use it, or how it relates to sibling tools like 'mold_stopVirtualMachine' or 'mold_waitForJob'. The description only states what the tool does, not when to invoke it.

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/ycyun/ablestack-MCP-server'

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