Skip to main content
Glama
pvliesdonk

markdown-vault-mcp

by pvliesdonk

Table of Contents

get_toc
Read-onlyIdempotent

Retrieve a heading outline for a note or folder subtree. Supports max level and limits on notes returned.

Instructions

Heading outline for a single note or a whole folder subtree.

If 'path' ends in '.md' it is a note: returns a flat ordered list of {heading, level} (the title as a synthetic H1). Otherwise 'path' is a folder: returns {path, notes, truncated} where 'notes' is an ordered list of {path, title, headings} aggregating every note under the subtree. Mirrors the 'toc://vault/{path}' resource, adding the max_level / max_notes controls below.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesNote path ("a/b.md") or folder prefix ("a/b").
max_levelNoDrop headings deeper than this level (e.g. 2 keeps H1-H2); must be >= 1. The synthetic H1 title always survives. Default None returns all levels.
max_notesNoFolder mode only — cap on distinct notes (default 200, must be >= 1). When more notes match, the first max_notes (by path) are returned and 'truncated' is True.
wait_for_pending_writesNoWhen True, wait until recent write/edit/delete/rename operations are applied to the index before answering. Default False answers from the current index; inspect '_meta.index_stale' to tell whether a write was still in flight. Bounded by a server timeout (default 60s).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral details: synthetic H1 title, folder aggregation with truncation, and wait_for_pending_writes affecting index staleness. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (three short paragraphs) with no wasted words. The first sentence immediately states the core purpose, and each subsequent sentence adds necessary detail without redundancy.

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?

The description covers all aspects: both modes, return structures, controls, and index behavior. An output schema exists, so return values are documented. Given tool complexity (4 params, conditional behavior), the description is fully informative.

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?

Schema coverage is 100%, so baseline is 3. The description adds context beyond schema: explains that synthetic H1 always survives max_level, that max_notes triggers 'truncated' flag, and that wait_for_pending_writes waits for index updates. This enhances parameter understanding.

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 it provides a heading outline for a note or folder subtree, with explicit distinction between path types (.md note vs folder). The specific verb 'returns flat ordered list' and 'aggregates every note' differentiates it from siblings like 'read' or 'browse_vault'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use note mode vs folder mode based on path ending, and mentions it mirrors the 'toc://vault/{path}' resource. However, it does not explicitly exclude use cases or compare with alternatives like 'search' or 'get_context'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pvliesdonk/markdown-vault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server