Skip to main content
Glama

stop_container

Stop a Proxmox container immediately by specifying the node and VMID.

Instructions

Stop a container (immediate)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesThe node name
vmidYesThe container VMID
Behavior3/5

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

Annotation destructiveHint=false already indicates non-destructive. Description adds 'immediate', implying a forced stop, but lacks details on consequences (e.g., unsaved work). Adequate but not thorough.

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?

Extremely short and to the point. While it lacks details, it is not verbose and front-loads the essential action. A bit too minimal for full value.

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 the existence of sibling 'shutdown_container', the description should differentiate when to use immediate stop vs graceful shutdown. It omits this crucial context and does not explain return values or behavior.

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?

Both parameters (node, vmid) are fully described in the schema, so the description adds no additional meaning. Baseline 3 applies.

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 'Stop' and resource 'container', and the parenthetical 'immediate' distinguishes it from a graceful shutdown, which is relevant given the sibling 'shutdown_container'.

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 on when to use this tool versus alternatives like 'shutdown_container' or 'reboot_container'. The description only implies immediate stop but does not explain context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredriksknese/mcp-proxmox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server