Skip to main content
Glama

Start, stop or restart VPS

vps_power
Destructive

Execute a power action on a VPS: start, stop, or restart. Synonyms accepted: 'reboot' → restart; 'shutdown' / 'poweroff' / 'power_off' → stop; 'power_on' / 'boot' → start. Stop and restart cause downtime — require confirm:true.

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "vps_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID (call vps_list to find it)
actionYesThe power action to perform. Canonical values: start | stop | restart. Synonyms are normalized.
confirmNoRequired (must be true) for 'stop' and 'restart' actions — they cause downtime. Not required for 'start'.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false; the description earns extra credit by specifying which actions cause downtime and that a confirmation flag gates them. It stops short of saying what happens when the VPS is already in the target state or whether the call is synchronous.

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?

Three short sentences, front-loaded with the core verb and the accepted actions, with the safety constraint last where it is most likely to be read before calling. The synonym list slightly duplicates the enum but remains useful for free-form agent input.

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?

For a 3-parameter mutation tool with no output schema, the definition covers purpose, accepted inputs, and the downtime/confirm safety contract. The main remaining gap is the return behavior (status payload, async vs. immediate), which nothing else in the definition supplies.

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%, so the schema already documents id, action (with enum and synonym note), and confirm. The synonym mapping in the description largely restates the enum contents rather than adding new 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?

States a specific verb and resource ('Execute a power action on a VPS') and immediately bounds it to three canonical actions: start, stop, restart. An agent can distinguish this from vps_reinstall_os, vps_cancel, or vps_get without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear in-context guidance: which actions are disruptive, that stop/restart require confirm:true, and that start does not. It does not name a sibling for related-but-different jobs (e.g. OS reinstall), so routing to alternatives is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.