Skip to main content
Glama
DustinTrap

kvm-pilot

by DustinTrap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_boot_device

Destructive

Set the next or persistent boot device via BootSourceOverride, or clear it with none. Check boot_options first to confirm the BMC allows the target.

Instructions

Set the next-boot (or persistent) boot device via BootSourceOverride. CONFIG MUTATION.

Gated by the config effect gate + per-invocation approval; denials come back through the same path with a typed outcome (#234). none clears the override; once=false makes it persistent; uefi=false selects legacy BIOS mode where the target exposes it. A target the BMC doesn't advertise fails fast (call boot_options first to see allowable).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
onceNoTrue = next boot only; false = persistent until cleared.
uefiNoTrue = UEFI boot mode; false = legacy BIOS where the BMC offers it.
deviceYesBoot source to override with; 'none' clears the override. Must be in boot_options' allowable list.
confirmNoPer-invocation approval when the client cannot prompt a human: set true to approve this exact call under the operator's standing policy. Leave false when the client supports elicitation (a human is asked). Never pre-set it speculatively; a denial returns outcome=not_confirmed.
profileNoProfile name from ~/.config/kvm-pilot/config.toml selecting which KVM/BMC (and its managed host) this call targets. Omit to use the server's default (KVM_PILOT_PROFILE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / confirm / description
      Added value: +"Per-invocation approval when the client cannot prompt a human: set true to approve this exact call under the operator's standing policy. Leave false when the client supports elicitation (a human is asked). Never pre-set it speculatively; a denial returns outcome=not_confirmed."
    • addedInput schema / properties / device / description
      Added value: +"Boot source to override with; 'none' clears the override. Must be in boot_options' allowable list."
    • addedInput schema / properties / once / description
      Added value: +"True = next boot only; false = persistent until cleared."
    • addedInput schema / properties / profile / description
      Added value: +"Profile name from ~/.config/kvm-pilot/config.toml selecting which KVM/BMC (and its managed host) this call targets. Omit to use the server's default (KVM_PILOT_PROFILE)."
    • addedInput schema / properties / uefi / description
      Added value: +"True = UEFI boot mode; false = legacy BIOS where the BMC offers it."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive/non-idempotent, and the description adds substantial context beyond them: it is a config mutation subject to the config effect gate plus per-invocation approval, denials return a typed outcome on the same path, and unadvertised targets fail fast. This is exactly the extra behavioral detail annotations cannot convey.

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?

Front-loaded with the mutation warning and quite dense for its length. The trailing issue reference '(#234)' is minor noise, and the clauses are packed, but nearly every sentence carries actionable content.

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?

For a destructive mutation tool with no output schema, the description covers approval behavior, the denial outcome, override-clearing semantics, and the fail-fast condition. An agent has everything needed to invoke it correctly and interpret the failure path.

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%, so once/uefi/device/confirm/profile are already fully documented in the schema. The description restates the none/once=false/uefi=false semantics, adding little beyond what the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource ('Set the next-boot (or persistent) boot device via BootSourceOverride') and immediately labels it a CONFIG MUTATION. It is clearly distinguishable from the read-only sibling boot_options, which it names explicitly.

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?

Gives the prerequisite workflow clearly ('call boot_options first to see allowable') and explains the gating/approval path. It stops short of an explicit when-not-to-use statement, but the fail-fast note and the boot_options pointer cover the practical routing decision.

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

Deploy Server

Other Tools