mcp-server-ovh

ovh_oauth2_initialize

Authenticates to OVH API using OAuth2 credentials to enable cloud infrastructure management.

Instructions

Initialize OVH API client with OAuth2 credentials

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": {
      "endpoint": "<endpoint>",
      "clientID": "<clientID>",
      "clientSecret": "<clientSecret>"
    },
    "name": "ovh_oauth2_initialize"
  }
}

Input Schema

Name	Required	Description
`clientID`	Yes	OAuth2 client ID
`endpoint`	Yes	OVH API endpoint
`clientSecret`	Yes	OAuth2 client secret

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.9Jul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention side effects (e.g., setting global client state), idempotency, or authentication requirements beyond the parameters.

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 concise sentence that directly states the tool's purpose with no filler or redundancy.

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?

The description is too brief for a tool with 3 required parameters and no output schema or annotations. It fails to explain that initialization is likely required before other API calls, and does not describe return values or state changes.

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?

The schema covers 100% of parameters with basic descriptions. The tool description adds no additional meaning beyond 'OAuth2 credentials', so it meets the baseline but does not enhance understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('initialize') and the resource ('OVH API client with OAuth2 credentials'). However, it does not differentiate from the sibling tool 'ovh_initialize_client', which likely serves a similar purpose but with different authentication methods.

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 is provided on when to use this tool versus alternatives like 'ovh_initialize_client'. The description lacks context on prerequisites or invocation order.

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

Deploy Server