IPI Provisioner MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

generate_bmc_test_script

Generate a bash script to test BMC connectivity for multiple hosts, returning a ready-to-run script for verifying IPMI or Redfish access.

Instructions

Generate a bash script to test BMC connectivity for multiple hosts.

Args: hosts: List of host configurations with BMC details

Returns: Bash script for testing BMC connectivity

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": {
      "hosts": "<hosts>"
    },
    "name": "generate_bmc_test_script"
  }
}

Input Schema

Name	Required	Description	Default
`hosts`	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.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It only states the tool generates a script and returns it, without mentioning side effects, permissions, or that it's non-destructive. Minimal transparency beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the main action, followed by Args and Returns sections. However, the Returns line largely repeats the first sentence ('Bash script for testing BMC connectivity'), introducing minor 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 tool has one complex parameter (hosts array) but its structure is undefined. The description does not explain what 'BMC details' include or what the generated script actually does beyond testing connectivity. Despite having an output schema, without input detail the description is incomplete for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only says 'List of host configurations with BMC details'. This adds some meaning but fails to specify required fields (e.g., IP, credentials, protocol), leaving the input insufficiently defined for a user to construct valid hosts.

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 the tool generates a bash script for testing BMC connectivity across multiple hosts. This specific verb+resource+scope distinguishes it from siblings like test_bmc_connection (which directly tests) and validate_bmc_addresses (which validates addresses).

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?

The description implies usage (generate a script rather than directly test) but provides no explicit guidance on when to choose this over alternatives like test_bmc_connection or validate_bmc_addresses. No when-to-use or exclusion criteria are given.

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