Skip to main content
Glama
Sign In
Nemeton MCP

Nemeton MCP

by juergenkoller-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

pause_vm

Temporarily halt a running VM to free up system resources or perform maintenance.

Instructions

Pause 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": {
      "vm": "<vm>"
    },
    "name": "pause_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmYesVM name or identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are absent, so the description must disclose behavioral traits. It fails to mention what happens to the VM (e.g., memory state preserved), whether operations are reversible, required permissions, or side effects. The single sentence adds no behavioral context beyond the basic action.

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 sentence with no wasted words. It is efficient for such a simple tool, though it could be slightly more informative without losing conciseness. Structurally it is front-loaded with the action.

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 no annotations, the description is incomplete. It fails to explain the VM's state after pausing, how to resume, or error scenarios. For a state-modifying operation, this level of detail is insufficient.

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?

Schema coverage is 100% with one parameter described as 'VM name or identifier'. The description adds no additional meaning or constraints beyond the schema. Baseline 3 is appropriate since the schema already clearly documents the parameter.

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 action 'Pause' and the resource 'running VM', using a specific verb-noun pair. It distinguishes from siblings like stop_vm or suspend_vm through the verb choice, but does not explicitly differentiate among them.

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 usage guidance is provided. The description does not indicate when to use pause_vm versus alternatives such as suspend_vm, stop_vm, or force_stop_vm. There are no exclusions, preconditions, or recommendations.

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