Skip to main content
Glama
Sign In
Unraid MCP

Unraid MCP

by lemanjo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Unraid API vms

unraid_v4371_query_vms
Read-onlyIdempotent

List all virtual machines on an Unraid server and display their current states. Use this tool to check which VMs are running, stopped, or paused for monitoring and management.

Instructions

List virtual machines and their states.

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": "unraid_v4371_query_vms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the output scope ('their states') and does not disclose additional behavioral traits such as whether only running VMs are included or how state is represented.

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?

The description is a single sentence that is front-loaded and directly states the action and subject. Every word earns its place; there is no fluff or repetition.

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?

For a simple, parameterless, read-only listing tool, the description is almost sufficient. It tells the agent what the action is and that the output includes virtual machines and their states, although an output schema would be needed for full return-structure clarity.

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 schema coverage is effectively complete. There are no parameter semantics for the description to clarify, so the baseline for a no-parameter tool 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 uses a specific verb ('List') and identifies the resource ('virtual machines') plus the key detail ('their states'). It is clear and unambiguous on its own, but it does not differentiate itself from the similarly named sibling tool unraid_list_vms.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool rather than alternatives. The sibling list includes unraid_list_vms, which appears to overlap significantly, and the description does not explain any distinction or selection criteria.

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