IPI Provisioner MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_installation_status

Retrieve the current installation status and progress for your OpenShift cluster using the installation directory. Determine if provisioning is ongoing, complete, or failed.

Instructions

Get cluster installation status.

Args: install_dir: Installation directory

Returns: Installation status and progress

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": {
      "install_dir": "<install_dir>"
    },
    "name": "get_installation_status"
  }
}

Input Schema

Name	Required	Description	Default
`install_dir`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full transparency burden. It implies a read-only operation via 'Get' and mentions return of 'status and progress', but does not disclose error behavior, required installation state, or other side effects.

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 extremely concise: a single clear sentence plus a simple Args/Returns block. No unnecessary words or redundant information.

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?

For a one-parameter read tool with an output schema, the description covers the core purpose and return summary. However, it omits usage context and behavioral details, making it adequate but not fully 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?

The input schema lists only install_dir with type string and 0% coverage. The description adds 'Installation directory' which gives basic meaning beyond the bare schema, but lacks details like path format or expected location.

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 states 'Get cluster installation status' with a specific verb and resource, clearly indicating the tool's function. It distinguishes itself from siblings like get_installation_logs by focusing on status rather than logs.

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?

The description provides no guidance on when to use this tool, no prerequisites, and no alternatives. It simply states the action without any contextual advice.

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