list_folderList immediate child folders, Markdown notes, and attachments in an Obsidian vault folder. Leave folder empty for root.
List the immediate child folders, Markdown notes, and attachments in one vault folder.
| Name | Required | Description | Default |
|---|---|---|---|
| folder | No | Vault-relative folder. Omit for the vault root. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by specifying 'immediate' children (non-recursive) and the types of items listed (folders, notes, attachments). This provides useful behavioral context beyond annotations.
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 a single sentence with no wasted words. It is front-loaded with the verb and scope, making it easy for an agent to quickly understand the tool's purpose.
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?
For a simple read-only list tool with one optional parameter and no output schema, the description is largely complete. It specifies what is listed and scoped. However, it does not describe the output format (e.g., list of paths or objects), which could be useful.
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 description coverage is 100% (the parameter 'folder' has a description). The overall description does not add additional meaning to the parameter beyond what the schema already provides, though it contextualizes the parameter within the list operation.
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 verb 'List' and the resource 'immediate child folders, Markdown notes, and attachments', scoped to 'one vault folder'. This distinguishes it from siblings like list_notes (which lists all notes) and vault_overview (broader).
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 implies usage for viewing contents of a single folder, but provides no explicit guidance on when to use this tool versus alternatives like list_notes or vault_overview. No exclusions or when-not-to-use are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.