Skip to main content
Glama
Sign In
mcp-1panel-plus

mcp-1panel-plus

by EC061
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Start, Stop, or Restart Container

operate_container

Execute safe start, stop, or restart lifecycle operations on a Docker container on a selected 1Panel node.

Instructions

Execute a safe container lifecycle operation (start, stop, or restart) on a Docker container on the selected node.

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": {
      "container": "<container>",
      "operation": "<operation>"
    },
    "name": "operate_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdNoTarget node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.local
containerYesContainer name or container ID.
operationYesLifecycle action: "start", "stop", or "restart".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description reinforces this by calling the operation 'safe', which is useful framing for a mutation tool. But it adds no operational detail such as whether stop is graceful vs forced, expected latency, or side effects on dependent services, so it exceeds the annotation bar only slightly.

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?

A single front-loaded sentence with the verb, resource and allowed values in one pass; nothing is padded. The word 'safe' is a slight filler qualifier but otherwise it is tight.

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

Completeness3/5

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

For a three-parameter mutation tool with full schema coverage and no output schema, the agent knows what to call but not what to expect on return, whether failures are retried, or what happens to a running container during stop. The essentials are present, but side-effect and outcome expectations are under-specified.

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 description coverage is 100%, with nodeId, container and the operation enum fully documented in-schema, so baseline 3 applies. The description merely restates the operation set already encoded in the enum and adds no format or usage nuance beyond it.

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?

States a specific verb ('execute a safe container lifecycle operation') plus the resource (Docker container) and enumerates the exact allowed operations (start/stop/restart), which cleanly separates it from read-oriented siblings like list_containers and get_container_logs. It stops short of naming any sibling as 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no prerequisites (e.g. container must exist, whether stop is graceful, whether restart briefly interrupts service). The only hint is 'on the selected node', which weakly implies the nodeId default of local.

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