Skip to main content
Glama
ycyun

ABLESTACK MOLD MCP Server

by ycyun

VM 정지

mold_stopVirtualMachine

Stop a virtual machine in ABLESTACK MOLD cloud infrastructure. Supports forced shutdown option and returns job ID for tracking.

Instructions

stopVirtualMachine(4.21). forced 옵션 지원. 반환에 jobid 포함 가능.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
forcedNo

Implementation Reference

  • Handler function that executes the tool by calling the generic MOLD API 'stopVirtualMachine' with provided arguments and returns the JSON response.
    async (args) => {
      const data = await callApi("stopVirtualMachine", args);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema defining parameters: id (required string), forced (optional boolean).
    inputSchema: {
      id: z.string(),
      forced: z.boolean().optional(),
    },
  • Registration of the 'mold_stopVirtualMachine' tool, including title, description, input schema, and handler function.
    server.registerTool(
      "mold_stopVirtualMachine",
      {
        title: "VM 정지",
        description: "stopVirtualMachine(4.21). forced 옵션 지원. 반환에 jobid 포함 가능.",
        inputSchema: {
          id: z.string(),
          forced: z.boolean().optional(),
        },
      },
      async (args) => {
        const data = await callApi("stopVirtualMachine", 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 the tool can return a jobid, which hints at asynchronous operation, but doesn't clarify if stopping is reversible, what permissions are needed, whether it affects running processes/data, or error conditions. The 'forced' option is mentioned but not explained behaviorally.

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

Conciseness3/5

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

The description is brief (one sentence fragment) but not particularly well-structured. It front-loads the function name with version, then mentions forced option, then return value - this ordering could be improved for clarity. While concise, it feels more like technical notes than a helpful description.

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 destructive VM operation with no annotations and no output schema, the description is inadequate. It doesn't explain what 'stopping' entails, whether data is preserved, what the jobid return means operationally, or error handling. The mention of version (4.21) adds some context but not enough for safe usage.

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?

With 0% schema description coverage for 2 parameters, the description adds minimal value. It mentions 'forced 옵션 지원' (forced option supported) for one parameter but doesn't explain what 'forced' means semantically or how it differs from regular shutdown. The 'id' parameter gets no explanation at all.

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 the tool stops a virtual machine, which is a clear verb+resource combination. However, it doesn't distinguish this from its sibling 'mold_startVirtualMachine' beyond the obvious action difference, nor does it specify if this is a graceful shutdown or immediate termination beyond the 'forced' parameter mention.

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 on when to use this tool versus alternatives. It mentions 'forced 옵션 지원' (forced option supported) but doesn't explain when to use forced vs non-forced shutdown, or how this relates to other VM management tools like 'mold_startVirtualMachine' or 'mold_waitForJob'.

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