Skip to main content
Glama

shell_df

Check disk space usage and monitor storage capacity to manage system resources effectively.

Instructions

Show disk usage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoCommand arguments

Implementation Reference

  • Configuration entry for 'shell.df' which is transformed into the MCP tool named 'shell_df'
    'shell.df': {
      command: 'df',
      description: 'Show disk usage',
      allowedArgs: ['-h', '-T', '--help'],
      timeout: 5000
    },
  • src/index.ts:27-43 (registration)
    Registers the 'shell_df' tool (among others) by transforming 'shell.df' key to 'shell_df' name and providing schema
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const tools = Object.entries(allowedCommands).map(([name, config]) => ({
        name: name.replace('shell.', 'shell_'),  // Replace shell. with shell_
        description: config.description,
        inputSchema: {
          type: "object",
          properties: {
            args: {
              type: "array",
              items: { type: "string" },
              description: "Command arguments"
            }
          }
        }
      }));
      return { tools };
    });
  • Input schema for shell_df tool: object with 'args' array of strings
    inputSchema: {
      type: "object",
      properties: {
        args: {
          type: "array",
          items: { type: "string" },
          description: "Command arguments"
        }
      }
    }
  • MCP tool call handler for shell_df: transforms 'shell_df' to 'shell.df', gets config, validates, executes 'df' command via executor, returns stdout
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      try {
        const command = String(request.params?.name || '');
        const fullCommand = `shell.${command.replace('shell_', '')}`;  // Replace shell_ back to shell.
        
        if (!(fullCommand in allowedCommands)) {
          return {
            content: [{ type: "text", text: `Unknown command: ${command}` }],
            isError: true
          };
        }
        
        const actualCommand = allowedCommands[fullCommand].command;
        const args = Array.isArray(request.params?.arguments?.args)
          ? request.params.arguments.args.map(String)
          : [];
      
        validator.validateCommand(actualCommand, args);
        const stream = await executor.execute(actualCommand, args);
      
        return {
          content: [{
            type: "text",
            text: await new Promise((resolve, reject) => {
              const chunks: Buffer[] = [];
              stream.stdout.on('data', (chunk: Buffer) => chunks.push(chunk));
              stream.stdout.on('end', () => resolve(Buffer.concat(chunks).toString()));
              stream.stdout.on('error', reject);
            })
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: `Command execution failed: ${error instanceof Error ? error.message : String(error)}` 
          }],
          isError: true
        };
      }
    });
  • Core execution logic: spawns the 'df' process with arguments and returns stdout stream
    async execute(
      command: string,
      args: string[] = [],
      options: ExecuteOptions = {}
    ): Promise<{ stdout: Readable }> {
      const commandKey = `${command} ${args.join(' ')}`;
      
      try {
        // Check security
        await this.securityChecker.validateCommand(command, args, options);
    
        // Check cache
        const cached = this.cache.get(commandKey);
        if (cached) {
          this.logger.debug('Using cached command result', { command, args });
          return this.createStreamFromCache(cached);
        }
    
        // Remove 'shell.' prefix for execution
        const baseCommand = command.replace('shell.', '');
    
        // Execute command
        this.logger.debug('Starting command execution', { command, args, options });
        const childProcess = spawn(baseCommand, args, {
          stdio: ['ignore', 'pipe', 'pipe'],
          timeout: options.timeout,
          cwd: options.cwd,
          env: {
            ...process.env,
            ...options.env
          },
          signal: options.signal
        });
    
        this.currentProcess = childProcess;
    
        // Error handling
        childProcess.on('error', (error: Error) => {
          this.logger.error('Command execution error', {
            command,
            args,
            error: error.message
          });
          throw new ToolError(
            'PROCESS_ERROR',
            'Command execution error',
            { command, args, error: error.message }
          );
        });
    
        // Timeout handling
        if (options.timeout) {
          setTimeout(() => {
            if (childProcess.exitCode === null) {
              this.logger.warn('Command execution timeout', {
                command,
                args,
                timeout: options.timeout
              });
              childProcess.kill();
              throw new ToolError(
                'TIMEOUT',
                'Command execution timeout',
                { command, args, timeout: options.timeout }
              );
            }
          }, options.timeout);
        }
    
        if (!childProcess.stdout) {
          throw new ToolError(
            'STREAM_ERROR',
            'Unable to get command output stream',
            { command, args }
          );
        }
    
        // Monitor process status
        childProcess.on('exit', (code, signal) => {
          this.logger.debug('Command execution completed', {
            command,
            args,
            exitCode: code,
            signal
          });
        });
    
        return {
          stdout: childProcess.stdout
        };
    
      } catch (error) {
        this.logger.error('Command execution failed', {
          command,
          args,
          error: error instanceof Error ? error.message : String(error)
        });
        
        throw new ToolError(
          'EXECUTION_ERROR',
          'Command execution failed',
          { 
            command, 
            args, 
            error: error instanceof Error ? error.message : String(error)
          }
        );
      }
    }
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 of behavioral disclosure. 'Show disk usage' implies a read-only operation, but it doesn't specify output format, potential side effects, or error conditions. For a shell command tool with no annotations, this leaves critical behavioral traits undocumented, such as how it interacts with the system or what permissions might be required.

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 very concise with just three words, making it front-loaded and efficient. However, it's arguably too brief, bordering on under-specification, which slightly reduces its effectiveness. Every word earns its place, but more detail could improve clarity without sacrificing conciseness.

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?

Given the complexity of a shell command tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, how to interpret results, or any dependencies. For a tool that likely outputs structured disk usage data, this lack of context makes it inadequate for an AI agent to use correctly without additional assumptions.

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 100% description coverage, with one parameter 'args' described as 'Command arguments'. The description adds no additional meaning beyond this, as it doesn't explain what arguments are valid or provide examples. With high schema coverage, the baseline score of 3 is appropriate, but the description doesn't compensate with any extra context.

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

Purpose3/5

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

The description 'Show disk usage' states the tool's purpose but is vague about what specific resource it operates on. It distinguishes from siblings like 'shell_cat' or 'shell_ps' by focusing on disk usage, but lacks specificity about whether it shows usage for filesystems, partitions, or directories. It's not tautological but could be more precise.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, and there's no reference to sibling tools for comparison. Users must infer usage from the name alone, which is insufficient for effective tool selection.

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/kevinwatt/shell-mcp'

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