markdown-vault-mcp

Folder Conventions

get_conventions

Read-onlyIdempotent

Retrieve the vault owner's authoring conventions for a note or folder, returning root rules first and the most specific last. Use it to apply correct formatting and structure before writing or editing.

Instructions

Return the vault owner's authoring conventions for a note or folder, vault root first and the most specific last.

Input Schema

Name	Required	Description	Default
`path`	No	A note or folder path, such as `"3-Resources/topic.md"` or `"3-Resources"`; a note takes its folder's conventions. `""` (the default) returns the root conventions and lists every folder that has its own.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv6.1.0Nov 2, 2026

changedInput schema / properties / path / description

Previous value: -"Relative note path (e.g. \"3-Resources/topic.md\") or folder\npath (e.g. \"3-Resources\"). A note path resolves to its\nparent folder. Pass \"\" (default) for discovery mode:\nvault-root conventions plus the full list of folders\ncarrying convention files."New value: +"A note or folder path, such as `\"3-Resources/topic.md\"` or `\"3-Resources\"`; a\nnote takes its folder's conventions. `\"\"` (the default) returns the root\nconventions and lists every folder that has its own."

Addedv4.0.0Aug 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral detail: results are ordered from root to most specific, and a note inherits its folder's conventions, which tells the agent how to interpret the output rather than repeating annotation data.

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?

A single tight sentence with the resource first and the ordering semantics trailing. Nothing is redundant and no sentence could be removed without losing information.

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

Completeness4/5

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

One optional parameter, an output schema, and full annotation coverage mean the description is nearly complete. It still leaves open what a 'convention' record contains and how precedence interacts with any explicit per-note overrides, but the output schema handles the return-shape gap.

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 description coverage is 100%, and the schema already explains the path parameter, the note-inherits-folder rule, and the empty-string default that returns root conventions plus a folder listing. The description's 'for a note or folder' only restates this, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Return the vault owner's authoring conventions for a note or folder.' This clearly separates it from data-reading siblings like read or list_documents, and the ordering clause ('vault root first and the most specific last') further pins down what is returned. It does not explicitly name the nearby context tools (vault_context, get_context, show_context) it could be confused with.

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

Usage Guidelines3/5

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

Usage is implied by the resource: call it to learn authoring conventions before writing. There is no explicit when-to-use statement, no exclusion, and no pointer to alternatives such as vault_context or get_context, which an agent might reasonably pick instead.

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