OVHcloud MCP Server

ovh_vps_stop

Stop a running OVH VPS to save costs or perform maintenance. This tool halts your VPS service immediately.

Instructions

Stop a running 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_stop"
  }
}

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

A3.5/5.0

Behavior2/5

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

No annotations exist, so the description must disclose behaviors. Only a vague 'careful!' is given, lacking detail on what stopping entails (e.g., power off, data loss, permission requirements).

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

Conciseness5/5

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

The description is a single sentence with a parenthetical warning, containing no fluff and efficient in conveying purpose.

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 simple tool structure (1 required param, no output schema), the description provides the core purpose but lacks details on return behavior, prerequisites, or side effects beyond the warning.

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 a good parameter description and example. The tool description adds no additional parameter context, so a 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 clearly states the action ('Stop a running VPS') and distinguishes it from siblings like start and reboot. The warning '(careful!)' adds nuance.

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

Usage Guidelines3/5

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

The description implies usage for stopping a running VPS but does not explicitly compare to alternatives (e.g., reboot). No when-not-to-use guidance is provided.

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