Nemeton MCP

Overview Schema Source Related Servers Discussions Admin

console_execute

Execute commands on a VM console and retrieve their output. Useful for scripting and troubleshooting virtual machines without direct GUI access.

Instructions

Run a command via the VM console and return its output.

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": {
      "vm": "<vm>",
      "command": "<command>"
    },
    "name": "console_execute"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	Yes	VM name or identifier
`command`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description bears full responsibility for behavioral disclosure. It only states basic functionality, omitting side effects (e.g., changes to VM state), error behavior, or required permissions.

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, clear sentence that conveys the core action. It is front-loaded and efficient, though it could benefit from expanded structure (e.g., bullet points for parameters).

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?

Given no output schema and minimal annotations, the description lacks completeness. It does not explain output format, error handling, or prerequisites (e.g., VM power state). Sibling tools like ssh_execute have more detailed descriptions.

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

Parameters2/5

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

Schema coverage is 50% (only 'vm' described). The description adds no parameter-level details beyond the schema, failing to explain the 'command' parameter format, constraints, or examples.

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?

The description clearly states the verb 'Run', the resource 'command via VM console', and the outcome 'return its output'. It distinguishes from sibling tools like ssh_execute and read_console by specifying 'console'.

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?

No guidance is provided on when to use this tool versus siblings like ssh_execute or read_console. The description does not mention prerequisites (e.g., VM must be powered on) or exclusions.

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