Engram Obsidian Memory Sync

List Folder Contents

list_folder

Read-onlyIdempotent

List the notes, attachments, and subfolders directly inside one folder. Pass an empty string for the vault root. Set recursive: true to list every descendant folder (with note counts) instead of just the direct ones. To see every folder in the vault with counts call list_folder with recursive: true on the root. To find notes by content use search_notes.

Input Schema

TableJSON Schema

Name	Required	Description
`folder`	No	Folder path (e.g. "Health") or "" for root. Defaults to root.
`vault_id`	No	Target vault: its name (e.g. "Engram") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve.
`recursive`	No	List every descendant folder, not just direct subfolders. Defaults to false.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes
`folder`	Yes	Folder listed; "" is the root
`folders`	Yes	Direct subfolders, or every descendant when recursive was true.
`attachments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / folder / description

Previous value: -"Folder path (e.g. \"Health\") or \"\" for root"New value: +"Folder path (e.g. \"Health\") or \"\" for root. Defaults to root."

addedInput schema / properties / recursive

Added value: +{
+  "description": "List every descendant folder, not just direct subfolders. Defaults to false.",
+  "type": "boolean"
+}

removedInput schema / required
```
Removed value: -[
-  "folder"
-]
```

addedOutput schema / properties / folders

Added value: +{
+  "description": "Direct subfolders, or every descendant when recursive was true.",
+  "items": {
+    "properties": {
+      "count": {
+        "description": "Notes directly inside",
+        "type": "integer"
+      },
+      "folder": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "folder",
+      "count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "folder",
-  "notes",
-  "attachments"
-]New value: +[
+  "folder",
+  "notes",
+  "attachments",
+  "folders"
+]

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / vault_id / description

Previous value: -"Target vault — its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault — the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."New value: +"Target vault: its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."

First observedSep 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description contributes extra context beyond the annotations, notably that recursive results include note counts and that only direct children are returned by default. It does not add return-format or pagination detail, but the output schema exists and covers that.

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?

Short and front-loaded, leading with what is listed before covering the recursive option and the search_notes alternative. Every sentence carries routing or scoping information, though the two recursive sentences partially overlap in intent.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Between the description, full schema coverage, and output schema, an agent has everything needed to call this correctly whether scoping to root, a subfolder, or a recursive walk.

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

Parameters3/5

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

Schema coverage is 100%, so folder, vault_id, and recursive are already documented in the schema, including the empty-string-for-root convention. The description largely restates those semantics and only marginally extends them by noting the note counts returned under recursive. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (list) and resource (notes, attachments, subfolders directly inside one folder), and distinguishes itself from siblings by naming search_notes for content-based lookup. An agent can tell it apart from get_notes, list_tags, or list_vaults without opening the schema.

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?

Gives explicit when-to-use routing: empty string for root, recursive=true for all descendants, root+recursive for every folder with counts, and search_notes for content search. Alternatives and the conditions selecting them are spelled out rather than implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Engram Obsidian Memory Sync tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.