List directory contents with detailed file information and optional filter patterns to quickly find specific files.
List contents of a directory with detailed information
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Directory path to list | |
| detailed | No | Show detailed information (like ls -la) | |
| filter | No | Optional file filter pattern (e.g., "*.txt", "*.ps1") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description only mentions 'detailed information' which mirrors the parameter. No disclosure of performance, access rights, or output structure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One clear sentence; appropriately short for a simple tool. Could be expanded with usage hints but not overly verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema; description fails to explain what the output contains (e.g., file names, sizes). Incomplete for agent decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with basic descriptions. The tool description adds no extra meaning beyond what the schema provides, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists directory contents with detailed information. It distinguishes from sibling tools like search-files and get-file-info, but doesn't explicitly differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., search-files). No exclusions or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gunjanjp/powershell-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server