Send advanced QMP commands to a managed Windows 98 VM's local QEMU endpoint for direct state inspection and control.
Run an advanced QMP command against a managed VM's local broker-owned QMP endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| vm_id | Yes | ||
| command | Yes | ||
| arguments | No |
Changes observed during successful MCP inspections.
v1.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations supply the fact that this is not read-only, not idempotent, and not marked destructive, but the description adds little behavioral detail beyond that. It does not state whether the VM must already be selected/managed, what side effects arbitrary QMP commands may have, or what the response contains; 'broker-owned endpoint' is unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no redundant phrases, and the execution verb is front-loaded. However, 'advanced' and 'broker-owned' add jargon without clarity, so it is not a perfect concise description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and sparse annotations, the description needs to explain return behavior, prerequisites, and relationship to sibling tools; it does none of these. A tool that can run arbitrary QMP commands is high-risk and needs more context than this.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description mentions none of the parameters. An agent gets no help understanding the expected QMP command format, how to pass arguments, or how vm_id relates to the managed VM.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Identifies a specific action ('Run') against a precise resource ('QMP endpoint of a managed VM'), and the QMP/HMP distinction separates it from qemu_hmp_command. However, the qualifier 'advanced' is vague and no sibling is named, so it does not fully disambiguate from overly similar QMP-related tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool rather than qemu_hmp_command, qemu_vm_command_preview, or qemu_doctor. The only hint is the word 'advanced,' which does not establish selection criteria or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.