Skip to main content
Glama
Wayazi

MCP File System

by Wayazi

get_file_info

Retrieve detailed information about a file or directory within the MCP File System by specifying its path. Streamline file management and access control queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to file or directory

Implementation Reference

  • Executes fs.stat on the validated path and returns structured file information including type, size, timestamps, and permissions as JSON.
    async ({ path: filePath }: { path: string }) => {
        try {
            const validPath = validatePath(filePath);
            const stats = await fs.stat(validPath);
            const info = {
                type: stats.isDirectory() ? 'directory' : 'file',
                size: stats.size,
                created: stats.birthtime,
                modified: stats.mtime,
                accessed: stats.atime,
                permissions: stats.mode.toString(8)
            };
            return { content: [{ type: 'text', text: JSON.stringify(info, null, 2) }] };
        } catch (error: any) {
            return { content: [{ type: 'text', text: `Error getting file info: ${error.message}` }] };
        }
    }
  • src/index.ts:151-170 (registration)
    Full registration of the get_file_info tool, specifying the name, Zod input schema, and inline asynchronous handler function.
    server.tool(
        "get_file_info",
        { path: z.string().describe("Path to file or directory") },
        async ({ path: filePath }: { path: string }) => {
            try {
                const validPath = validatePath(filePath);
                const stats = await fs.stat(validPath);
                const info = {
                    type: stats.isDirectory() ? 'directory' : 'file',
                    size: stats.size,
                    created: stats.birthtime,
                    modified: stats.mtime,
                    accessed: stats.atime,
                    permissions: stats.mode.toString(8)
                };
                return { content: [{ type: 'text', text: JSON.stringify(info, null, 2) }] };
            } catch (error: any) {
                return { content: [{ type: 'text', text: `Error getting file info: ${error.message}` }] };
            }
        }
  • Zod input schema for the tool, defining a required 'path' parameter as a string with description.
    { path: z.string().describe("Path to file or directory") },
  • Helper function used by the handler (and other tools) to resolve and validate the file path is within allowed directories, throwing an error if not.
    function validatePath(filePath: string): string {
        const absolutePath = path.resolve(filePath);
        if (!allowedDirs.some(dir => absolutePath.startsWith(path.resolve(dir)))) {
            throw new Error(`Access denied: ${filePath} is not within allowed directories`);
        }
        return absolutePath;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/Wayazi/mcp_file_system'

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