Skip to main content
Glama
DustinTrap

kvm-pilot

by DustinTrap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

events

Read-onlyIdempotent

Collect read-only typed device signals from the kvmd stream, bounded by count or 30s duration, to diagnose ATX, MSD, and streamer state changes or verify vision waits.

Instructions

Collect typed device events from the kvmd stream (read-only, bounded).

MCP twin of CLI events minus follow mode (#233 — an endless stream doesn't fit the synchronous stdio transport): returns up to count events or duration seconds' worth (capped 30 s), whichever first. logs is the better first diagnostic; events add the live typed stream (atx/msd/streamer state changes) to cross-check a vision wait against.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoStop after this many events.
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).
durationNoStop after this many seconds (capped at 30), whichever comes first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / count / description
      Added value: +"Stop after this many events."
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / duration / description
      Added value: +"Stop after this many seconds (capped at 30), whichever comes first."
    • addedInput schema / properties / duration / exclusiveMinimum
      Added value: +0
    • 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)."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description still adds real value beyond them: the operation is bounded (up to count events or duration seconds, capped 30s), and follow mode is deliberately omitted due to synchronous stdio transport. That framing of boundedness and the CLI divergence is genuinely informative, though return-shape details are absent.

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 purpose and bounds before the sibling comparison and the #233 rationale. The CLI-twin and issue-reference aside is somewhat layered, but each sentence contributes routing or behavioral context rather than 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?

No output schema exists, yet the description explains what an event is (typed atx/msd/streamer state changes) and how the call terminates (count/duration). That covers most of what an agent needs to call it correctly; only explicit return formatting is left unstated.

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%, and the schema already documents count, duration, and the 'whichever comes first' cap. The description restates the count/duration interaction and the 30s cap but adds no format or syntax detail beyond the schema, so the baseline of 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 and resource ('Collect typed device events from the kvmd stream') and immediately scopes it with '(read-only, bounded)'. It also differentiates from siblings by contrasting with the CLI twin and naming the content of the stream (atx/msd/streamer state changes). An agent can distinguish this from logs and wait_for_state without opening a 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 routes the agent: '``logs`` is the better first diagnostic; events add the live typed stream ... to cross-check a vision wait against.' This states both the alternative and the conditions selecting each, which is exactly what usage guidance should do.

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