OVHcloud MCP Server

ovh_vps_ips

List all IP addresses assigned to a VPS by providing the VPS service name.

Instructions

List all IPs assigned to a 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_ips"
  }
}

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 provided, and description only states the action. Missing disclosure on permissions, rate limits, error handling, or pagination. Minimal behavioral info.

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?

Single sentence, no unnecessary words. Front-loaded with 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?

Adequate for a simple list tool, but lacks output schema or description of return format. Could be improved with expected output details.

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 described. Description adds no additional meaning beyond the schema, so baseline of 3.

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?

Description clearly states 'List all IPs assigned to a VPS', with specific verb and resource. Distinguishes from sibling tools like ovh_vps_info and ovh_vps_list.

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?

Implied context (use when needing IPs of a VPS), but no explicit when-not-to-use or alternatives. Does not mention relationship to ovh_vps_info which might also provide IPs.

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