Ploi.io MCP Server

Get Ploi Docker container

ploi_get_container

Read-onlyIdempotent

Retrieve details for a specific Docker container on a Ploi server using its server ID and container ID.

Instructions

Retrieve details for a single Docker container on a Ploi server.

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>",
      "container_id": "<container_id>"
    },
    "name": "ploi_get_container"
  }
}

Input Schema

Name	Required	Description	Default
`server_id`	Yes	Ploi server ID.
`container_id`	Yes	Ploi Docker container ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive action. Description adds 'Retrieve details' which aligns but provides no additional behavioral context beyond what annotations offer.

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 of 12 words, no wasted words, purpose is front-loaded.

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?

For a simple retrieval tool with two well-documented parameters and no output schema, the description is adequate. Could optionally mention what details are returned, but not necessary.

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% for both parameters, so baseline 3. Description does not add additional meaning beyond the schema descriptions.

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 verb 'Retrieve', resource 'details for a single Docker container', and context 'on a Ploi server'. Distinguishes from sibling tools like ploi_list_containers (list all) and ploi_create_container.

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?

Usage is implied from the purpose (retrieve a specific container), but no explicit guidance on when not to use it or alternatives among the many container-related siblings (list, create, update, delete, etc.).

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