kvm-pilot

mount_iso

Idempotent

Attach a local or remote ISO as virtual media to a KVM/BMC-managed host for OS installs or recovery; optionally present it as a USB drive instead of a CD-ROM.

Instructions

Mount an ISO as virtual media on the host. GATED act (media effect gate); reversible.

source is a local path or an http(s):// URL; usb=true attaches as a USB flash drive instead of a CD-ROM. Needs KVM_PILOT_MCP_ALLOW_MEDIA + per-invocation approval. Mounting bumps the frame generation, so a mouse click planned against the pre-mount screen is invalidated.

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": {
      "source": "<source>"
    },
    "name": "mount_iso"
  }
}

Input Schema

Name	Required	Description
`usb`	No	True presents it as a USB flash drive instead of a CD-ROM.
`name`	No	Image name to store it under on the device; defaults to the source's basename.
`source`	Yes	Local path on the server host, or an http(s):// URL the device fetches/streams.
`confirm`	No	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.
`profile`	No	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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Oct 19, 2026

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 / name / description

Added value: +"Image name to store it under on the device; defaults to the source's basename."

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 / source / description

Added value: +"Local path on the server host, or an http(s):// URL the device fetches/streams."

addedInput schema / properties / usb / description

Added value: +"True presents it as a USB flash drive instead of a CD-ROM."

First observedv0.1.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false), and the description adds substantial non-structured context: the media-effect gate, the required env flag and approval flow, reversibility, and the critical side effect that mounting bumps frame generation, invalidating a previously planned mouse click. That is exactly the behavioral detail structured fields cannot carry.

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-loads the action and gate status, then details parameters and side effects; every sentence carries information. The inline-code markup adds minor visual noise but no padding.

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?

With no output schema, the description covers the gate, approval requirement, reversibility, and the frame-generation side effect an agent must account for. It omits edge cases such as what happens if media is already mounted, keeping it just short of 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?

Schema description coverage is 100%, so all five parameters are already documented (source, usb, name, confirm, profile). The description restates source semantics (local path or http(s) URL) and usb behavior without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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 and resource ("Mount an ISO as virtual media on the host") and is immediately distinguishable from siblings like list_virtual_media and eject. An agent can identify the action without opening the schema.

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 concrete preconditions for use: it is a gated act requiring KVM_PILOT_MCP_ALLOW_MEDIA plus per-invocation approval, and notes the operation is reversible. It does not explicitly route the agent to alternatives (e.g., ejecting existing media first), so it falls short of a full when/when-not/alternative statement.

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