Skip to main content
Glama
wonderwhy-er

Claude Desktop Commander MCP

get_file_info

Retrieve comprehensive metadata about files or directories, including size, timestamps, permissions, type, and text file details like line count and append position. Works within allowed paths; use absolute paths for reliability.

Instructions

                    Retrieve detailed metadata about a file or directory including:
                    - size
                    - creation time
                    - last modified time 
                    - permissions
                    - type
                    - lineCount (for text files)
                    - lastLine (zero-indexed number of last line, for text files)
                    - appendPosition (line number for appending, for text files)
                    
                    Only works within allowed directories.
                    
                    IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths.
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • Main handler function that executes the get_file_info tool: parses input schema, calls helper getFileInfo, formats output as key-value text.
    export async function handleGetFileInfo(args: unknown): Promise<ServerResult> {
        try {
            const parsed = GetFileInfoArgsSchema.parse(args);
            const info = await getFileInfo(parsed.path);
            return {
                content: [{
                    type: "text",
                    text: Object.entries(info)
                        .map(([key, value]) => `${key}: ${value}`)
                        .join('\n')
                }],
            };
        } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            return createErrorResponse(errorMessage);
        }
    }
  • Zod schema for validating get_file_info tool input: requires 'path' string.
    export const GetFileInfoArgsSchema = z.object({
      path: z.string(),
    });
  • Registration/dispatch: Maps 'get_file_info' tool calls to handleGetFileInfo handler in the CallToolRequest switch statement.
    case "get_file_info":
        result = await handlers.handleGetFileInfo(args);
        break;
  • src/server.ts:622-643 (registration)
    Tool registration in ListToolsRequest handler: defines name, description, input schema for get_file_info.
        name: "get_file_info",
        description: `
                Retrieve detailed metadata about a file or directory including:
                - size
                - creation time
                - last modified time 
                - permissions
                - type
                - lineCount (for text files)
                - lastLine (zero-indexed number of last line, for text files)
                - appendPosition (line number for appending, for text files)
                
                Only works within allowed directories.
                
                ${PATH_GUIDANCE}
                ${CMD_PREFIX_DESCRIPTION}`,
        inputSchema: zodToJsonSchema(GetFileInfoArgsSchema),
        annotations: {
            title: "Get File Information",
            readOnlyHint: true,
        },
    },
  • Core helper function that retrieves file stats (size, times, type, permissions) and optionally line count for text files.
    export async function getFileInfo(filePath: string): Promise<Record<string, any>> {
        const validPath = await validatePath(filePath);
        const stats = await fs.stat(validPath);
    
        // Basic file info
        const info: Record<string, any> = {
            size: stats.size,
            created: stats.birthtime,
            modified: stats.mtime,
            accessed: stats.atime,
            isDirectory: stats.isDirectory(),
            isFile: stats.isFile(),
            permissions: stats.mode.toString(8).slice(-3),
        };
    
        // For text files that aren't too large, also count lines
        if (stats.isFile() && stats.size < FILE_SIZE_LIMITS.LINE_COUNT_LIMIT) {
            try {
                // Get MIME type information
                const { mimeType, isImage, isPdf } = await getMimeTypeInfo(validPath);
    
                // Only count lines for non-image, likely text files
                if (!isImage && !isPdf) {
                    const content = await fs.readFile(validPath, 'utf8');
                    const lineCount = countLines(content);
                    info.lineCount = lineCount;
                    info.lastLine = lineCount - 1; // Zero-indexed last line
                    info.appendPosition = lineCount; // Position to append at end
                }
            } catch (error) {
                // If reading fails, just skip the line count
                // This could happen for binary files or very large files
            }
        }
    
        return info;
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: path normalization, absolute vs relative path reliability, tilde path limitations, and directory restrictions. It doesn't mention error handling or performance characteristics, but covers key operational constraints.

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 appropriately sized and front-loaded with the core purpose. The bulleted list efficiently conveys what metadata is returned. The path guidance is necessary but could be slightly more concise. The DC reference at the end feels slightly extraneous but doesn't significantly detract.

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

Completeness4/5

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

For a single-parameter read operation with no annotations and no output schema, the description is quite complete. It explains what metadata is returned, path requirements, and operational constraints. The main gap is lack of explicit mention of error conditions or return format, but given the tool's relative simplicity, it's reasonably comprehensive.

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

Parameters4/5

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

With 0% schema description coverage for the single 'path' parameter, the description compensates well by explaining path requirements: must be absolute for reliability, paths are normalized, relative paths may fail, tilde paths might not work. This adds crucial semantic context beyond the bare schema.

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

Purpose5/5

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

The description clearly states the verb 'retrieve' and resource 'detailed metadata about a file or directory', with specific examples of what metadata is included. It distinguishes from siblings like list_directory (which lists contents) and read_file (which reads content).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Only works within allowed directories' and 'Always use absolute paths for reliability'. It also distinguishes from alternatives by specifying it retrieves metadata, not content or listings.

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/wonderwhy-er/DesktopCommanderMCP'

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