Skip to main content
Glama
Sign In
windows98-mcp

windows98-mcp

by ido-pluto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vm_list

Read-onlyIdempotent

Lists every named VM known to the broker, showing connection, build, address, capabilities, and lease state.

Instructions

List every named VM known to this broker with its current connection, build, address, capabilities, and lease state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vm_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds scope and returned fields but no additional behavioral traits such as whether this triggers a refresh or requires a selected broker, so it adds moderate value 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?

A single, front-loaded sentence with no filler. It states the action, scope, and key returned fields in one pass, so every word earns its place.

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 read-only, zero-parameter listing tool, the description is complete: it identifies the resource scope and exactly what information will be returned. No output schema exists, but the description supplies the necessary return information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema covers 100% of them, so there is nothing for the description to clarify. The no-parameter baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action ('List'), a specific resource scope ('every named VM known to this broker'), and the fields returned (connection, build, address, capabilities, lease state). It is clear, but it does not explicitly contrast itself with the sibling qemu_vm_list, so the differentiation is only implicit.

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?

The description gives clear context for use: use this tool when you need a full inventory of broker-known VMs and their current state. It does not provide explicit when-not-to-use guidance or name alternatives such as qemu_vm_list or vm_status, so it stops short of a 5.

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