Skip to main content
Glama
montyanderson

transmission-mcp

Check Free Disk Space

transmission_free_space
Read-onlyIdempotent

Checks free disk space at a specified path, defaulting to the download directory, to verify storage availability for torrent downloads.

Instructions

Check available disk space at a given path.

This tool checks how much free space is available at the specified path. If no path is provided, it checks the default download directory.

Args:

  • path (string, optional): Path to check (defaults to download directory)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Available free space in bytes and human-readable format

Examples:

  • Use when: "How much disk space is available?"

  • Use when: "Check free space in /downloads" -> params with path="/downloads"

  • Use when: "Do I have enough space for more downloads?"

Error Handling:

  • Returns error if path doesn't exist or is not accessible

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to check free space for (defaults to download directory)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already indicate this is a safe, read-only, idempotent operation. The description adds behavioral context: default download directory behavior and error handling for non-existent/inaccessible paths.

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 well-structured with sections (Args, Returns, Examples, Error Handling), concise without unnecessary words, and front-loaded with the main purpose.

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 read-only tool with two parameters and no output schema, the description covers all essential aspects: purpose, parameters, examples, and error handling. Return value description could be more structured but suffices.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters. The description adds value by including usage examples and clarifying the 'path' default, going 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's purpose: checking free disk space at a given path. It uses a specific verb and resource, and distinguishes from sibling tools that handle torrent operations.

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 description provides explicit usage examples ('Use when: ...'), making it clear when to invoke this tool. However, it does not mention when not to use it or suggest alternatives among siblings.

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/montyanderson/transmission-mcp'

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