Skip to main content
Glama

liara_delete_vm

Delete a virtual machine from the Liara cloud platform by specifying its VM ID to remove infrastructure resources.

Instructions

Delete a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmIdYesThe VM ID to delete

Implementation Reference

  • The core handler function that implements deleting a Liara virtual machine (VM) by its ID. It validates the VM ID, creates a specialized IaaS API client, and sends a DELETE request to the Liara IaaS API endpoint `/vm/{vmId}`.
    export async function deleteVM(
        client: LiaraClient,
        vmId: string
    ): Promise<void> {
        validateRequired(vmId, 'VM ID');
        const iaasClient = createIaaSClient(client);
        await iaasClient.delete(`/vm/${vmId}`);
    }
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. 'Delete' implies a destructive, irreversible mutation, but the description doesn't specify whether this requires special permissions, confirmation steps, or has side effects (e.g., associated resources like disks or networks). It also omits details like response format, error conditions, or rate limits, leaving the agent with insufficient operational context.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, adhering perfectly to conciseness principles without being under-specified in this minimal context.

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 tool's complexity (destructive mutation with no annotations and no output schema), the description is incomplete. It lacks critical context like irreversible consequences, permission requirements, or what happens to dependent resources. For a high-stakes operation like VM deletion, this minimal description fails to provide the necessary completeness for safe and effective use by an agent.

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?

The input schema has 100% description coverage, with 'vmId' clearly documented as 'The VM ID to delete'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or sourcing hints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 clearly states the action ('Delete') and resource ('a virtual machine'), making the purpose immediately understandable. It distinguishes from sibling tools like 'liara_get_vm' or 'liara_create_vm' by specifying deletion rather than retrieval or creation. However, it doesn't explicitly differentiate from other deletion tools like 'liara_delete_app' or 'liara_delete_database' beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the VM must exist or be stopped), consequences (e.g., data loss, billing implications), or when to choose deletion over other actions like stopping or snapshotting. With many sibling tools including other deletions, this lack of context is a significant gap.

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/razavioo/liara-mcp'

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