OVHcloud MCP Server

ovh_vps_snapshot

Retrieve details of a VPS snapshot by providing the service name.

Instructions

Get VPS snapshot information

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

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

B3.4/5.0

Behavior2/5

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

No annotations are present, and the description only states 'get information' without disclosing behavioral traits such as read-only nature, required permissions, or handling of missing snapshots.

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?

The description is a single, concise sentence with no wasted words, though it could be slightly more informative without sacrificing brevity.

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 simple get operation with one parameter and no output schema, the description is adequate but omits details about the return format or error conditions, leaving some ambiguity.

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 only parameter. The description adds no additional meaning beyond what the schema provides.

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 'Get VPS snapshot information' uses a specific verb and resource, clearly distinguishing from sibling tools like 'ovh_vps_create_snapshot' and 'ovh_vps_info'.

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 a simple retrieval use case but provides no guidance on when to use this tool versus alternatives like 'ovh_vps_info' or 'ovh_vps_list'.

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