Skip to main content
Glama

Delete Virtual_machine

netbox_delete_virtual_machine
Destructive

Deletes a virtual machine in NetBox by numeric ID. Irreversible: also removes all dependent objects (interfaces, IPs, etc.) via cascade. Confirm the exact object before use.

Instructions

Delete a virtual_machine from NetBox by numeric id.

DESTRUCTIVE and IRREVERSIBLE. NetBox CASCADES deletes: removing an object also removes everything that depends on it (deleting a device removes its interfaces, power ports, and assigned IPs; deleting a site can remove its racks, devices, and prefixes; deleting a manufacturer removes its device types; and so on). There is no undo. Confirm the exact object — and what will cascade with it — with the user before calling.

Returns a confirmation on success (NetBox replies HTTP 204 No Content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric id of the virtual_machine to delete.
Behavior5/5

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

Describes cascading delete behavior (e.g., deleting a device removes interfaces, etc.) and mentions the HTTP 204 response. Annotations already indicate destructiveHint, but the description adds important context beyond annotations.

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?

Description is concise with four sentences, front-loaded with the action and key warnings. Every sentence adds value without redundancy.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description fully covers what the tool does, how to use it, what response to expect, and important consequences.

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 coverage is 100%, and the description reiterates the parameter's purpose without adding new semantics. Baseline score of 3 is appropriate as no extra value is provided.

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?

Clearly states 'Delete a virtual_machine from NetBox by numeric id.' It uses a specific verb and resource, differentiating from sibling tools that delete other objects.

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

Usage Guidelines5/5

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

Explicitly warns that the operation is destructive and irreversible, and advises confirming with the user to avoid unintended cascading deletions. Provides clear when-not-to-use guidance.

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/ZenixSolutions/netbox-mcp-server'

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