OVHcloud MCP Server

ovh_vps_start

Start a stopped OVH VPS using its service name. Use this tool to power on a VPS instance.

Instructions

Start a stopped VPS

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_start"
  }
}

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.9/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the action is asynchronous, whether it requires special permissions, or the resulting state of the VPS.

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 front-loaded and concise, but it is overly terse. It earns its place in terms of brevity but lacks valuable context that would help the agent.

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?

Given the tool's simplicity (one required parameter, no output schema), the description is minimally viable. However, it does not explain what 'start' entails (e.g., state transition, response), so it is not fully complete.

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% and the schema already describes the 'serviceName' parameter with an example. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 'Start a stopped VPS' clearly states the action (start) and the resource (VPS), distinguishing it from sibling tools like ovh_vps_stop and ovh_vps_reboot.

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, nor any mention of prerequisites (e.g., VPS must be stopped). The context is only implied by the description.

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