qbt-kit

qbt_call

Call any qBittorrent WebUI API endpoint by scope/name when built-in tools lack coverage. Validates params and enforces confirmation for destructive calls plus read-only protection.

Instructions

Call any qBittorrent endpoint directly as scope/name, for anything the tools above do not cover. Parameters are validated against the endpoint spec, and the same safety gates apply: destructive endpoints need confirm, and read-only mode refuses anything that mutates state.

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": {
      "path": "<path>"
    },
    "name": "qbt_call"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	scope/name, e.g. torrents/pieceStates
`params`	No	endpoint parameters
`confirm`	No	required for destructive endpoints

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that params are validated against the endpoint spec, that destructive endpoints require 'confirm', and that read-only mode refuses state-mutating calls. It does not describe error behavior or pagination, but the safety-gate disclosure is substantive and non-obvious.

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?

Two tight sentences with no filler. The fallback purpose is front-loaded in the first clause and the safety behavior follows, so an agent gets the key facts immediately.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, routing, validation, and safety gates. What remains thin is guidance on malformed paths or how endpoint-specific params are shaped, but nothing essential to invoking it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so path, params, and confirm are already documented in the schema; baseline is 3. The description only reinforces the 'scope/name' path format and the confirm-for-destructive rule, adding little beyond what structured fields already state.

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?

States a specific verb and resource ('Call any qBittorrent endpoint directly as scope/name') and explicitly positions itself as the fallback: 'for anything the tools above do not cover.' An agent can distinguish it from the specific siblings like list_torrents or add_torrent without opening any schema.

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 phrase 'for anything the tools above do not cover' clearly conditions when to reach for this generic tool instead of the purpose-built siblings, which is exactly the routing decision an agent faces. It stops short of naming a specific sibling or listing explicit exclusions, so it is clear context rather than a full when/when-not statement.

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

This server cannot be deployed