Skip to main content
Glama
Negm-Ahmed

Desktop Commander

by Negm-Ahmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_file_info

Retrieve detailed metadata for a file or directory, including size, timestamps, permissions, type, and text-file line information. Use absolute paths within allowed directories.

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

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.5/5.0
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.

Deploy Server

Other Tools