list_folderList files in any folder by absolute path, optionally filtering with a glob pattern to locate specific file types like *.R or *.md.
List files in a folder.
Args:
folder_path: Absolute path to the folder.
pattern: Glob pattern to filter files (e.g. "*.R", "*.md"). Default: all files.
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | No | * | |
| folder_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It only states the action without disclosing side effects, limitations (e.g., recursion, size limits), permissions, or read-only nature. Minimal transparency.
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?
The description is short and front-loaded with a clear purpose statement. The 'Args' section is minimal and directly adds value. No unnecessary words.
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?
Given the simple tool purpose and the existence of an output schema, the description covers input parameters adequately. However, it lacks behavioral details like recursion behavior, but is otherwise complete for a basic file-listing operation.
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 0%, but the description provides explicit descriptions for both parameters (folder_path and pattern), including the pattern format with examples. This adds meaningful context beyond the schema's default value and type.
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 'List files in a folder' with a specific verb and resource. Among many sibling tools like list_backups or list_basket, list_folder is distinct in its purpose of listing files in a file system folder.
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?
The description provides no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context for when it is appropriate to call list_folder over other listing or scanning tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.