Skip to main content
Glama

qui_system

Perform qBittorrent system management tasks including license activation, authentication changes, and instance operations via the qui-mcp server.

Instructions

qui system operations on qui. Pass operation and an arguments object; path variables go directly in arguments, query values in arguments.params, and a JSON request body in arguments.body.

  • qui_activate_license: POST /license/activate

  • qui_change_password: PUT /auth/change-password

  • qui_check_setup: GET /auth/check-setup

  • qui_create_api_key: POST /api-keys/

  • qui_create_arr_instance: POST /arr/instances

  • qui_create_client_api_key: POST /client-api-keys/

  • qui_create_external_program: POST /external-programs/

  • qui_create_filter_view: POST /filter-views/

  • qui_create_notification_target: POST /notifications/targets

  • qui_create_tracker_customization: POST /tracker-customizations/

  • qui_delete_api_key: DELETE /api-keys/{id}

  • qui_delete_arr_instance: DELETE /arr/instances/{id}

  • qui_delete_client_api_key: DELETE /client-api-keys/{id}

  • qui_delete_external_program: DELETE /external-programs/{id}

  • qui_delete_filter_view: DELETE /filter-views/{id}

  • qui_delete_license: DELETE /license/{licenseKey}

  • qui_delete_notification_target: DELETE /notifications/targets/{id}

  • qui_delete_tracker_customization: DELETE /tracker-customizations/{id}

  • qui_execute_external_program: POST /external-programs/execute

  • qui_get_application_info: GET /application/info

  • qui_get_arr_instance: GET /arr/instances/{id}

  • qui_get_current_user: GET /auth/me

  • qui_get_dashboard_settings: GET /dashboard-settings

  • qui_get_latest_version: GET /version/latest

  • qui_get_licensed_status: GET /license/licensed

  • qui_get_log_exclusions: GET /log-exclusions

  • qui_get_log_settings: GET /log-settings

  • qui_get_tracker_icons: GET /tracker-icons

  • qui_get_version: GET /version

  • qui_list_api_keys: GET /api-keys/

  • qui_list_arr_instances: GET /arr/instances

  • qui_list_client_api_keys: GET /client-api-keys/

  • qui_list_custom_themes: GET /themes/custom

  • qui_list_external_programs: GET /external-programs/

  • qui_list_filter_views: GET /filter-views/

  • qui_list_licenses: GET /license/licenses

  • qui_list_log_files: GET /logs/files

  • qui_list_notification_events: GET /notifications/events

  • qui_list_notification_targets: GET /notifications/targets

  • qui_list_tracker_customizations: GET /tracker-customizations/

  • qui_refresh_licenses: POST /license/refresh

  • qui_resolve_arr: POST /arr/resolve

  • qui_test_arr_connection: POST /arr/test

  • qui_test_arr_instance: POST /arr/instances/{id}/test

  • qui_test_notification_target: POST /notifications/targets/{id}/test

  • qui_update_arr_instance: PUT /arr/instances/{id}

  • qui_update_dashboard_settings: PUT /dashboard-settings

  • qui_update_external_program: PUT /external-programs/{id}

  • qui_update_filter_view: PUT /filter-views/{id}

  • qui_update_log_exclusions: PUT /log-exclusions

  • qui_update_log_settings: PUT /log-settings

  • qui_update_notification_target: PUT /notifications/targets/{id}

  • qui_update_tracker_customization: PUT /tracker-customizations/{id}

  • qui_validate_license: POST /license/validate

  • qui_validate_session: GET /auth/validate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No behavioral details are provided. The description only lists HTTP methods and paths, without explaining side effects, permissions, side effects, or what each operation does. Since no annotations are present, the description carries the full burden and fails to disclose any behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficient in that it avoids redundant prose and simply lists the operations with their HTTP methods. It is well-structured as a list, making it easy to scan, though the length is inherent to the number of operations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the large number of operations and a generic schema, the description is severely incomplete. It does not provide per-operation inputs, outputs, or error conditions. There is no mention of return values or expected outcomes, making it impossible to understand how to use each operation effectively.

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?

The description explains that 'arguments' contains path variables, query params, and a request body, which gives some structure to the generic arguments object. However, it does not specify which arguments each operation expects, and the schema has no per-operation parameter definitions. The explanation is generic and not very helpful for understanding required parameters.

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

Purpose1/5

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

The description simply states 'qui system operations on qui' and then lists a long series of endpoint names without explaining what the tool actually does as a whole or what each operation accomplishes. It fails to convey the purpose beyond being a generic API wrapper for many unrelated actions.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the sibling tools (e.g., qui_cross_seed). The description provides no context for selecting this tool or specific operations within it, aside from the raw list of endpoints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arr-mcps/qui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server