OVHcloud MCP Server

ovh_ssh_check

Test SSH connectivity to a remote server by verifying host, port, username, password, or private key authentication.

Instructions

Test SSH connectivity to a remote server

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ovh_ssh_check"
  }
}

Input Schema

Name	Required	Description
`host`	No	SSH host (default: SSH_HOST env)
`port`	No	SSH port (default: SSH_PORT env or 22)
`username`	No	SSH username (default: SSH_USER env)
`password`	No	SSH password (default: SSH_PASSWORD env)
`privateKeyFile`	No	Path to SSH private key file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jun 8, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavior such as authentication method, success/failure handling, or side effects. Only states 'test' without detail.

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 wasted words. Front-loaded with action and resource. Very concise.

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?

No output schema exists, so description should explain return values. It does not. Also lacks prerequisites or error conditions. Incomplete for a tool with 5 parameters.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter.

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 the tool tests SSH connectivity to a remote server. The verb 'Test' is specific and distinct from sibling 'ovh_ssh_exec' which executes commands.

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 provided on when to use this tool vs alternatives like ovh_ssh_exec. The tool's purpose is implied but not explicitly contrasted with siblings.

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