Nemeton MCP

by juergenkoller-software

Overview Schema Source Related Servers Discussions Admin

Local

get_vm

Retrieve configuration and current state of a specified virtual machine.

Instructions

Get configuration and current state of a single 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": {
      "vm": "<vm>"
    },
    "name": "get_vm"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool 'gets' data, which implies read-only, but does not disclose any behavioral details such as authentication requirements, error handling for missing VMs, or whether the state is real-time or cached. This is a significant gap for a tool with no annotation support.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and resource, earning its place.

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?

Given the tool's simplicity (one required parameter, no nested objects, no output schema), the description is largely sufficient. However, it omits details on return format or error behavior, which would be helpful for a complete understanding.

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 input schema has 100% description coverage for the single parameter 'vm', so the schema itself fully documents it. The description does not add any additional semantics or constraints beyond what the schema provides, meeting the baseline for high 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 clearly states the tool retrieves 'configuration and current state' for a single VM, distinguishing it from list_vms (list all) and other VM manipulation tools. However, it could be more specific about what constitutes configuration and state.

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?

Usage context is implied by the tool name and description: use this tool to get details about a specific VM. No explicit comparison to sibling tools like list_vms or select_vm is provided, so the agent must infer when to use this over alternatives.

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