Unraid MCP

Unraid API pluginInstallOperation

unraid_v4371_query_plugin_install_operation

Read-onlyIdempotent

Retrieve details and capped output for a specific plugin installation operation using its operation ID.

Instructions

Get one tracked plugin installation including its capped output.

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": {
      "operationId": "<operationId>"
    },
    "name": "unraid_v4371_query_plugin_install_operation"
  }
}

Input Schema

Name	Required	Description	Default
`operationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 30, 2026

TDQS

A3.7/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, and the description does not contradict them. The phrase 'capped output' adds useful behavioral context, but it does not explain what 'tracked' means, how output is capped, or any authorization requirements.

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. Every word contributes: the verb, the resource, and the distinguishing 'capped output' detail.

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 operation with strong annotations and no output schema, the description conveys the core purpose and a key caveat. It would be slightly stronger if it pointed to the plural operation as the source of operationId values or clarified 'capped output,' but nothing essential is missing for making a correct call.

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%, and the description does not explain the operationId parameter beyond implying it identifies an installation. With one required parameter and no schema documentation, the description should compensate by clarifying the expected value or how to obtain it, which it does not.

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'), identifies a precise resource ('one tracked plugin installation'), and adds a distinguishing detail ('including its capped output'). This differentiates it from the plural sibling query_plugin_install_operations without needing to open the schema.

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 singular 'one' implies this tool is the by-id counterpart to query_plugin_install_operations, but it never explicitly names the sibling or states when to choose this over the list operation. The usage context is inferable but not directly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server