Skip to main content
Glama
Sign In
Windows Sandbox MCP

Windows Sandbox MCP

by xxmisaoxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sandbox_restart

Destructive

Destroy the current Windows guest and create a fresh session; disk changes are not preserved.

Instructions

Destroy current guest and create fresh session. Guest disk is not recovered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sandbox_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_mbNo
networkingNo
startup_timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds the crucial consequence the annotation can't express: the guest disk is not recovered, so prior state is permanently lost. It does not mention rate limits, permissions, or whether other host-side resources survive, so it falls short of 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?

Two short sentences, the destructive effect is front-loaded, and every clause carries information. No padding whatsoever.

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

Completeness3/5

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

For a destructive tool the description covers the single most important fact (irreversible disk loss), and there is no output schema to explain. However, with zero parameter documentation and no mention of permissions or side effects on host resources, it leaves the caller under-informed for a 3-parameter destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all three parameters (memory_mb, networking, startup_timeout) are bare titles with defaults. The description supplies no meaning for any of them, leaving the agent to guess units, valid ranges, and whether they affect the fresh session's configuration.

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?

"Destroy current guest and create fresh session" gives a specific verb pair and the resource it acts on, clearly distinguishing a restart/reset from the sandbox_start/sandbox_stop siblings in the lifecycle family. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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?

There is no guidance on when to choose this over sandbox_start, sandbox_stop, or sandbox_launch, all of which live in the same lifecycle family. The only hint is the implied intent of wanting a clean state, which the agent must infer.

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