Skip to main content
Glama

fs_stat

Retrieve file or directory statistics from remote servers via SSH to check permissions, size, and modification details for system monitoring and management.

Instructions

Gets file or directory statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSSH session ID
pathYesPath to stat

Implementation Reference

  • Handler implementation for the fs_stat tool, responsible for getting file or directory statistics on the remote system using SFTP.
    export async function statFile(
      sessionId: string,
      path: string
    ): Promise<FileStatInfo> {
      logger.debug('Getting file stats', { sessionId, path });
      
      const session = sessionManager.getSession(sessionId);
      if (!session) {
        throw new Error(`Session ${sessionId} not found or expired`);
      }
      
      try {
        const stats = await session.sftp.stat(path);
        
        let type: FileStatInfo['type'] = 'other';
        if ((stats as any).isFile && (stats as any).isFile()) {
          type = 'file';
        } else if ((stats as any).isDirectory && (stats as any).isDirectory()) {
          type = 'directory';
        } else if ((stats as any).isSymbolicLink && (stats as any).isSymbolicLink()) {
          type = 'symlink';
        }
        
        const statInfo: FileStatInfo = {
          size: stats.size,
          mtime: new Date((stats as any).mtime ? (stats as any).mtime * 1000 : Date.now()),
          mode: stats.mode,
          type
        };
        
        logger.debug('File stats retrieved', { sessionId, path, type, size: stats.size });
        return statInfo;
      } catch (error) {
        logger.error('Failed to get file stats', { sessionId, path, error });
        throw wrapError(
          error,
          ErrorCode.EFS,
          `Failed to get stats for ${path}. Check if the path exists.`
        );
      }
    }
  • Input validation schema for the fs_stat tool parameters.
    export const FSStatSchema = z.object({
      sessionId: z.string().min(1),
      path: z.string().min(1)
    });
  • src/mcp.ts:440-445 (registration)
    Registration and tool call handler in the switch-case logic of the SSH MCP server, which parses the arguments and invokes statFile.
    case 'fs_stat': {
      const params = FSStatSchema.parse(args);
      const result = await statFile(params.sessionId, params.path);
      logger.info('Path stat', { sessionId: params.sessionId, path: params.path });
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but lacks behavioral details: it doesn't specify what statistics are returned (e.g., size, permissions, timestamps), whether it works on symbolic links, error conditions (e.g., if path doesn't exist), or if it requires specific permissions. This is a significant gap for a tool with no annotation coverage.

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 extremely concise—a single sentence with no wasted words—and front-loaded with the core purpose. Every word earns its place, making it easy to parse quickly.

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 (a filesystem operation with no annotations and no output schema), the description is incomplete. It doesn't explain what statistics are returned, error handling, or how it interacts with sibling tools. For a tool that likely returns structured data, more context is needed to be fully helpful.

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%, with both parameters (sessionId and path) clearly documented in the schema. The description adds no additional meaning beyond the schema, such as explaining path formats or sessionId usage context. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Gets') and the resource ('file or directory statistics'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like fs_list or fs_read, which also operate on filesystem resources, so it doesn't reach the highest score.

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. With siblings like fs_list (for listing contents) and fs_read (for reading file content), there's no indication of when stat is preferred, such as for metadata retrieval without reading file data.

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/oaslananka/mcp-ssh-tool'

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