boxes-mcp

Overview Schema Source Related Servers Discussions Admin

boxes.capabilities

Report the observed display and interaction capabilities of a running virtual machine, including keyboard, mouse, clipboard, and drag-and-drop support.

Instructions

Report observed display and interaction capability state for a running VM

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": {
      "nameOrUuid": "<nameOrUuid>"
    },
    "name": "boxes.capabilities"
  }
}

Input Schema

Name	Required	Description
`probeQmp`	No
`nameOrUuid`	Yes	Domain name or UUID
`probeSpice`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 22, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description alone must reveal behavioral traits. 'Report' implies a read-only observation, but the optional probeQmp and probeSpice flags suggest active probing behavior that is never disclosed. The description does not say whether probing causes side effects, requires guest cooperation, or changes the result set.

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?

The description is a single, front-loaded sentence with no filler or repetition. It conveys the core operation efficiently, though it omits detail that would make it more informative.

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

Completeness2/5

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

For a tool with no output schema, no annotations, and two undocumented probe parameters, one sentence is not enough context. It does not clarify what capabilities are reported, what probing does, what the output looks like, or what happens if the VM is not running.

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 only 33%, and the description adds no information about probeQmp, probeSpice, or how they affect the reported capabilities. The two probe parameters remain semantically unexplained, so the description fails to compensate for the low schema coverage.

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?

The description says 'Report observed display and interaction capability state for a running VM', which names a specific verb, resource, and scope. It is clearly distinct from sibling tools like boxes.keyboard or boxes.display, though it does not explicitly name an alternative.

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

Usage Guidelines3/5

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

The phrase 'for a running VM' implies this tool is used to inspect capabilities of an active VM, and the purpose is reasonably inferable. However, it gives no explicit guidance about when not to use it or how it compares to siblings such as boxes.info or boxes.display.

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