IPI Provisioner MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create_baremetal_host_entry

Generate a baremetal host configuration for install-config.yaml by entering name, role, BMC details, and boot MAC. Returns a dictionary ready for cluster provisioning.

Instructions

Create a baremetal host entry for install-config.yaml.

Args: name: Host name (e.g., 'master-0') role: Host role ('master' or 'worker') bmc_address: BMC address (e.g., 'redfish://192.168.1.100') bmc_username: BMC username bmc_password: BMC password boot_mac_address: Boot MAC address (e.g., 'aa:bb:cc:dd:ee:ff') root_device_hint: Optional root device hint (e.g., '/dev/sda' or 'wwn')

Returns: Host configuration dictionary ready for install-config.yaml

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": {
      "name": "<name>",
      "role": "<role>",
      "bmc_address": "<bmc_address>",
      "bmc_username": "<bmc_username>",
      "bmc_password": "<bmc_password>",
      "boot_mac_address": "<boot_mac_address>"
    },
    "name": "create_baremetal_host_entry"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`role`	Yes
`bmc_address`	Yes
`bmc_password`	Yes
`bmc_username`	Yes
`boot_mac_address`	Yes
`root_device_hint`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states the tool returns a dictionary ('Returns: Host configuration dictionary ready for install-config.yaml'), indicating it's a pure data constructor rather than a side-effecting file operation. It does not explicitly say 'does not modify files', but the return statement strongly implies it.

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 well-organized docstring with a one-line summary followed by Args and Returns sections. Every sentence provides useful information; there is no fluff or repetition of schema details.

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

Completeness5/5

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

Given the tool's simplicity (7 scalar parameters, no nested objects) and detailed parameter examples, the description is complete. It explains the return value, which is especially important since the output schema is not visible to the agent. No critical context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by listing every parameter with concrete examples (e.g., name: 'master-0', bmc_address: 'redfish://192.168.1.100'). This adds significant meaning beyond the bare input schema, especially for root_device_hint with its optional/null type.

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 uses a specific verb ('Create') and resource ('baremetal host entry for install-config.yaml'), clearly distinguishing it from siblings like list_config_templates or validate_install_config. The purpose is unambiguous and concrete.

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 implies usage context: this tool constructs a single host entry for an install-config file. It does not explicitly mention alternatives or exclusions, but the purpose is clear enough that an agent would know when to use it over other tools like validate_network_cidr or generate_install_config.

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