Skip to main content
Glama
Sign In
vmware-sandbox-mcp

vmware-sandbox-mcp

by rumenjordanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sandbox_destroy

Permanently shut down and delete a sandbox and everything inside it. Copy out files first; this is irreversible and frees a sandbox slot.

Instructions

Shut down a sandbox and permanently delete it and everything inside it.

Use this as soon as you no longer need a sandbox; only a few can exist at once. Copy out any files you want to keep first, because this cannot be undone. Returns a short confirmation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sandbox_id": "<sandbox_id>"
    },
    "name": "sandbox_destroy"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandbox_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the critical behaviors: irreversibility ('cannot be undone'), total data loss ('everything inside it'), and a capacity limit on concurrent sandboxes. Missing only permission/auth requirements and whether destruction is immediate or eventual, keeping it below a 5.

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 short sentences, front-loaded with the irreversible destructive action, then usage guidance, then the data-safety warning. Nothing is redundant and the warning ordering is well matched to the risk.

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

Completeness4/5

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

An output schema exists, so the return value needs no explanation, and the 'copy out files first' caution covers the main pre-call pitfall. Minor gaps remain around required permissions and whether the sandbox must be running, but nothing essential to a correct call is absent.

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 description coverage is 0% and the single parameter 'sandbox_id' is documented nowhere, but the description makes clear by implication that it targets one specific sandbox. It adds no format, source, or how-to-obtain guidance for that ID, so a mid score is appropriate for a one-param tool.

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?

States a specific verb and resource — 'Shut down a sandbox and permanently delete it and everything inside it' — and distinguishes itself from siblings like sandbox_stop or sandbox_list by emphasizing permanent deletion of contents, not just stopping the process.

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?

Gives clear timing guidance ('as soon as you no longer need a sandbox') and a constraint-driven reason ('only a few can exist at once'). It does not explicitly name sandbox_stop as the non-destructive alternative for a sandbox you intend to reuse, which keeps it from a 5.

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

Deploy Server

Other Tools