Skip to main content
Glama
Sign In
fast-filesystem-mcp

fast-filesystem-mcp

by efforthye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fast_get_disk_usage

Retrieve disk usage information for a specified path. Quickly check available space and usage statistics to manage filesystem capacity effectively.

Instructions

Gets disk usage information

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath to check/

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / path / description
      Previous value: -"조회할 경로"New value: +"Path to check"
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It offers no information about permissions, error handling, or side effects. The minimal description does not compensate for the missing annotations.

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

Conciseness3/5

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

The description is very concise but lacks structure and detail. While brevity is good, it omits important information that could be included without excessive length. It is front-loaded but incomplete.

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

Completeness2/5

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

The tool has no output schema, so the description should clarify what disk usage information is returned (e.g., size, free space, etc.). It fails to provide this context, making it incomplete for a simple tool.

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?

The input schema has one parameter with 100% coverage. The description adds no additional meaning beyond the schema's 'Path to check'. The baseline score of 3 is appropriate since schema already documents the parameter.

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 'Gets disk usage information' clearly states the action and resource. It is distinct from sibling tools, which focus on file operations. However, it could be more specific about what disk usage information is provided (e.g., total, used, free).

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 is provided on when to use this tool or how it differs from alternatives. The description does not mention any prerequisites, limitations, or exclusions, leaving the agent without context for appropriate invocation.

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