OVHcloud MCP Server

ovh_vps_reboot

Reboot an OVHcloud VPS by specifying its service name. Useful for applying updates or fixing system issues.

Instructions

Reboot a VPS (careful!)

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": {
      "serviceName": "<serviceName>"
    },
    "name": "ovh_vps_reboot"
  }
}

Input Schema

Name	Required	Description	Default
`serviceName`	Yes	VPS service name (e.g. vps-xxxxxxxx.vps.ovh.net)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jun 8, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only warns 'careful!' but does not disclose consequences such as downtime, data loss, or the need for proper shutdown. Minimal transparency for a destructive action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (two words plus warning). While efficient, it lacks any structural elements that would aid understanding. Adequate for a simple tool but could be more informative.

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?

The tool is a mutation with no output schema and no annotations. The description fails to mention return behavior, side effects, or any post-reboot state. Incomplete for a potentially disruptive operation.

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 well-described in the schema. The description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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 'Reboot a VPS (careful!)' clearly states the action (reboot) and resource (VPS). It is a specific verb+resource pair, but it does not differentiate from sibling tools like start or stop, which is acceptable given the distinct action.

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 is provided on when to use this tool versus alternatives like start or stop. The exclamation 'careful!' implies caution but does not specify prerequisites or scenarios where reboot is appropriate.

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