Skip to main content
Glama
Sign In
Unraid MCP

Unraid MCP

by lemanjo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Unraid API upsDeviceById

unraid_v4371_query_ups_device_by_id
Read-onlyIdempotent

Retrieve a specific UPS device by its unique ID. Use this to fetch a single UPS unit's details, status, and configuration from Unraid.

Instructions

Get one UPS device by its schema-defined string ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds only the schema-defined ID qualification and no additional behavioral context such as not-found behavior or return format.

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, front-loaded sentence with no filler. Every word contributes to identifying the operation and its input.

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 one-parameter read-only tool with strong annotations, the description and schema are largely sufficient. The only minor gap is not describing the expected output shape, but that is not critical given the tool's simplicity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter semantics. It only restates that the ID is schema-defined and a string, without explaining what the ID refers to, how to obtain it, or any constraints beyond minLength 1.

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?

The description uses a specific verb ('Get') and resource ('one UPS device') and pinpoints the selection criterion ('by its schema-defined string ID'). This clearly differentiates the tool from the plural sibling unraid_v4371_query_ups_devices.

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

Usage Guidelines3/5

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

The description implies usage: call this when you need a single UPS device by ID. However, it does not explicitly state when not to use it or point to alternatives such as query_ups_devices for listing all devices.

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