Skip to main content
Glama
DustinTrap

kvm-pilot

by DustinTrap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

type_text

Destructive

Type printable text on a managed host's console through the HID keyboard for commands, installer fields, or passwords; no Enter is sent, so submit separately.

Instructions

Type a string on the managed host's console over the HID keyboard. DESTRUCTIVE.

For printable text (commands, installer fields, passwords); nothing echoes back and no Enter is appended — press_key('Enter') to submit. Keys that aren't text go through press_key; chords through send_shortcut. Keystrokes land wherever the host's focus is: snapshot first to confirm the screen, and after to see the effect. Needs KVM_PILOT_MCP_ALLOW_HID

  • per-invocation approval (elicitation, or confirm=true under standing policy). Returns the typed act outcome (receipt, or the denial reason).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesPrintable text to type verbatim. Press Enter separately with press_key('Enter').
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. Changed3 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 / 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 / text / description
      Added value: +"Printable text to type verbatim. Press Enter separately with press_key('Enter')."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely new behavior: nothing echoes back, no Enter is appended, keystrokes land wherever the host's focus is, and it requires KVM_PILOT_MCP_ALLOW_HID plus per-invocation approval (elicitation or confirm=true). It even names the denial outcome. This is context beyond the annotations.

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?

Front-loaded with the action and the DESTRUCTIVE label, then each subsequent sentence carries unique, non-redundant information (echo behavior, alternatives, focus, auth, return). No filler.

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?

With no output schema, the description compensates by describing the return value (typed act outcome: receipt or denial reason) and the full auth/approval path. An agent has everything needed to invoke this destructive tool correctly.

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 the schema already documents text, confirm, and profile in detail. The description reinforces that text is typed verbatim with no Enter appended, but this largely restates what the schema's text description already says, so baseline 3 is appropriate.

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 (type) on a specific resource (a string on the managed host's console over the HID keyboard) and immediately routes non-text keys to press_key and chords to send_shortcut, so the agent can distinguish it from siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers when to use (printable commands, installer fields, passwords), when not to (non-text keys -> press_key, chords -> send_shortcut), and the surrounding workflow (snapshot before to confirm focus, after to see effect). Prerequisites for approval are also stated.

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