Ploi.io MCP Server

Start custom server installation

ploi_start_custom_server_installation

After running the returned SSH command, start the installation for a custom Ploi server.

Instructions

Start installation for a custom Ploi server after the returned SSH command has been run.

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": {
      "server_id": "<server_id>"
    },
    "name": "ploi_start_custom_server_installation"
  }
}

Input Schema

Name	Required	Description
`server_id`	Yes	Ploi server ID.
`webhook_url`	No	Webhook called when server installation completes.
`install_monitoring`	No	Whether to install monitoring.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate mutability (readOnlyHint=false) and non-idempotency. The description adds the SSH command precondition, but does not disclose what happens on failure or if the SSH command hasn't been run. Adequate but not rich.

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 one sentence that is front-loaded and contains no redundant words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core action and precondition. However, it could be improved by noting that installation may be asynchronous or that it returns immediately, given no output schema. Still largely complete.

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%, so each parameter already has a description. The tool description does not add additional meaning beyond the schema, so baseline 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 it starts the installation for a custom Ploi server after a prerequisite SSH command has been run. This distinguishes it from sibling tools like ploi_create_custom_server (which creates the server) and ploi_restart_server.

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

Usage Guidelines4/5

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

The description explicitly states the precondition 'after the returned SSH command has been run,' providing a clear when-to-use condition. However, it does not explicitly list alternatives or when not to use.

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