vmware-sandbox-mcp

Overview Schema Source Related Servers Discussions Admin

sandbox_copy_in

Copies a file or folder from your designated transfer folder into a sandbox so it has a script, dataset, or project to work on. Only paths inside the transfer folder are allowed.

Instructions

Copy a file or a whole folder from the user's computer into a sandbox.

Use this to give the sandbox something to work on (a script, a dataset, a project folder). Only things inside the user's designated transfer folder can be copied; nothing else on the user's computer is reachable.

host_path: the file or folder to copy, relative to the transfer folder (for example "data/input.csv" or "myproject"). Paths that leave the transfer folder are rejected. guest_path: full destination path inside the sandbox. For a file, the path of the file itself (for example "/home/debian/input.csv"); its folder must already exist. For a folder, the path the folder should have (for example "/home/debian/myproject"); it is created if missing, and the folder's contents are placed inside it.

Folders are copied with everything in them. Files arrive without the executable flag (use chmod +x if needed). A folder that contains links is refused. Returns a short confirmation with the number of files and the size.

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>",
      "host_path": "<host_path>",
      "guest_path": "<guest_path>"
    },
    "name": "sandbox_copy_in"
  }
}

Input Schema

Name	Required	Description	Default
`host_path`	Yes
`guest_path`	Yes
`sandbox_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the transfer-folder confinement, rejection of escaping paths, folder auto-creation, non-preservation of the executable bit, refusal of folders containing links, and that a summary confirmation is returned. These are exactly the behavioral traits an agent needs before invoking a write-side transfer.

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

Conciseness4/5

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

It front-loads the purpose, then breaks the two non-obvious parameters into labeled blocks, then lists caveats. It is longer than a typical description, but the length is justified by the total absence of schema documentation; nothing reads as filler.

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?

For a mutation tool with no annotations, the definition covers constraints, destination semantics, caveats, and even the shape of the return, so an output schema is not strictly needed for the summary line. The only omission is any mention of sandbox_id.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for host_path and guest_path with format examples and the differing file-vs-folder semantics for the destination. It never explains sandbox_id, which is the one remaining gap given all three parameters are required and undocumented in the schema.

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 (copy), a specific resource (a file or whole folder), and an explicit direction (from the user's computer into a sandbox). The directionality alone distinguishes it from the sibling sandbox_copy_out.

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 context for when to use it ('to give the sandbox something to work on') with concrete examples of the payload types. It does not explicitly name the reverse-direction sibling as an alternative, but the in/out distinction is unambiguous.

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

Deploy Server