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

vmware-sandbox-mcp

by rumenjordanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sandbox_screenshot

Captures the sandbox's current display as a PNG image to inspect graphical programs, boot or error screens, or stuck commands; pixel positions in the image support click targeting.

Instructions

Take a picture of what is currently on a sandbox's screen.

Use this to see things that have no text output: a graphical program, a boot or error screen, or to check what the sandbox is displaying when a command seems stuck. For the output of commands, sandbox_run is faster and more precise.

Returns a PNG image of the sandbox's display at this moment. Positions in this image, counted in pixels from its top-left corner, are what sandbox_click expects.

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_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandbox_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 largely meets it: it discloses the return artifact ('Returns a PNG image'), the temporal semantics ('at this moment'), and the coordinate frame that sandbox_click consumes. It does not state what happens if the sandbox is not running or stopped, or whether the call has any cost/side effects, which are realistic failure contexts for a sandbox tool.

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, front-loaded blocks: purpose, usage with an explicit alternative, then return value and coordinate mapping. Every sentence adds information an agent needs; no filler or restated title.

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?

No output schema exists, and the description does the work of explaining the return (PNG of the display) plus the pixel-origin convention that ties into sandbox_click. The only material gap is prerequisites, e.g. whether the sandbox must be started first via sandbox_start.

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 single required parameter has 0% schema description coverage, so the description must compensate; it only implies a sandbox selector through the phrase 'a sandbox's screen' without explaining the identifier's format or how to obtain it. The added meaning is marginal but the parameter is self-evident in context.

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 ('Take a picture of what is currently on a sandbox's screen') and immediately frames itself against a named sibling by saying sandbox_run is better for command output. An agent can distinguish this from sandbox_run or sandbox_check without opening a schema.

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?

Gives concrete when-to-use cases (graphical program, boot or error screen, checking a stuck command) and an explicit when-not-to-use with the alternative named ('For the output of commands, sandbox_run is faster and more precise'). This is the routing guidance the dimension asks for.

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