rclone-mcp

core_quit

Terminate the running rclone process, optionally specifying an exit code to control shutdown behavior.

Instructions

Terminate rclone — Stops the rclone process, optionally supplying an exit code.

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

Input Schema

Name	Required	Description
`_async`	No	Run the command asynchronously. Returns a job id immediately.
`_group`	No	Assign the request to a custom stats group.
`exitCode`	No	Optional exit code to use when terminating the rclone process.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions termination but does not disclose behavioral traits such as side effects (e.g., killing all operations), authentication requirements, or asynchronous behavior. The _async parameter hints at async execution, but the description doesn't clarify its implications.

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 with no waste, front-loading the core action and then the optional parameter. It achieves clarity with minimal text.

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

Completeness3/5

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

For a simple quit action, the description is somewhat complete, but it lacks details on return values or confirmation of success. Given no output schema, more information on what the agent can expect after calling would improve completeness.

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 the schema already documents parameters. The description adds the context that exitCode is optional, but the schema also says 'Optional exit code'. Thus, the description adds minimal value beyond the schema.

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 clearly states the tool terminates rclone, a distinct action from all sibling tools. It uses specific verb 'Terminate' and specifies the resource 'rclone process', making it unambiguous.

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 this is the tool to quit rclone, but it does not provide explicit guidance on when it should be used versus alternatives, nor scenarios where it should be avoided. The context from sibling tools suggests it's unique, but the description could explicitly state that.

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

Deploy Server