Skip to main content
Glama
Sign In
rclone-mcp

rclone-mcp

by rclone-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

operations_size

Get aggregate size, file count, and count of objects without size metadata for a remote.

Instructions

Count remote size — Reports total size, file count, and number of objects without size metadata.

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

Input Schema

NameRequiredDescriptionDefault
fsNoRemote name or path to measure aggregate size information for.
_asyncNoRun the command asynchronously. Returns a job id immediately.
_groupNoAssign the request to a custom stats group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must convey all behavioral traits. It indicates the output (size, file count, objects without size metadata) but does not explicitly state read-only nature, side effects, or error conditions. The description partially fulfills the burden but lacks explicit safety declarations.

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 that front-loads the core purpose ('Count remote size') followed by specific outputs. Every word is informative with no redundancy.

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?

Given no output schema, the description sufficiently covers the return values (total size, file count, objects without size metadata). However, it does not address potential error conditions or behavior of async/group parameters, but for a simple counting tool this is largely adequate.

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 explains the parameters (fs, _async, _group) adequately. The description adds no additional semantic value beyond what is in the schema, maintaining the baseline score.

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

Purpose4/5

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

The description clearly states the tool counts remote size and reports total size, file count, and objects without size metadata. The verb 'Count' and resource 'remote size' are specific, and the output details distinguish it from siblings like operations_about and core_du, though not explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, suitable contexts, or exclusions, leaving the agent to infer usage from the name alone.

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