Skip to main content
Glama
ai-yliu

Filesystem MCP Server

by ai-yliu

get_file_info

Retrieve metadata for files or directories, including details like size, type, and permissions, to analyze and manage filesystem content.

Instructions

Get detailed file/directory metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the file or directory

Implementation Reference

  • Handler for the 'get_file_info' tool. Validates the path, retrieves file stats using fs.stat, formats the information using the formatFileInfo helper, and returns it as JSON-formatted text content.
    case 'get_file_info': {
      const { path: filePath } = request.params.arguments as { path: string };
      validatePath(filePath);
      
      const stats = await fs.stat(filePath);
      const fileInfo = formatFileInfo(filePath, stats);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(fileInfo, null, 2),
          },
        ],
      };
    }
  • src/index.ts:208-221 (registration)
    Tool registration in the listTools response, including name, description, and input schema definition.
    {
      name: 'get_file_info',
      description: 'Get detailed file/directory metadata',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the file or directory',
          },
        },
        required: ['path'],
      },
    },
  • Helper function that transforms fs.Stats object into a detailed file information object with path, size, type, timestamps, and permissions.
    function formatFileInfo(filePath: string, stats: Stats): Record<string, any> {
      return {
        path: filePath,
        size: stats.size,
        type: stats.isDirectory() ? 'directory' : 'file',
        created: stats.birthtime.toISOString(),
        modified: stats.mtime.toISOString(),
        accessed: stats.atime.toISOString(),
        permissions: {
          readable: stats.mode & fs.constants.R_OK ? true : false,
          writable: stats.mode & fs.constants.W_OK ? true : false,
          executable: stats.mode & fs.constants.X_OK ? true : false,
        }
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves metadata, implying a read-only operation, but doesn't specify permissions required, error conditions (e.g., if the path doesn't exist), rate limits, or what 'detailed' metadata includes. This leaves significant gaps for a tool with no annotation support.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and wastes no space, making it easy for an agent 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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed metadata' includes (e.g., file size, permissions, timestamps), potential errors, or how it differs from sibling tools. This lack of context makes it incomplete for effective agent use.

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 the 'path' parameter clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as path format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate.

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's purpose with a specific verb ('Get') and resource ('detailed file/directory metadata'), making it immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'list_directory' or 'search_files', which might also provide metadata, 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 like 'list_directory' or 'search_files'. It lacks context about whether this is for single-item metadata retrieval versus listing or searching, leaving the agent to infer usage from the tool name alone.

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/ai-yliu/filesystem-mcp-server'

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