Skip to main content
Glama
wirux

mcp-markdown-vault

View

view

Read markdown note content, explore directory structure, and search by heading or full-text query.

Instructions

Read and search markdown notes. Vault scope: general markdown notes vault. Actions: search (heading-aware fragment retrieval with TF-IDF + proximity), semantic_search (vector + lexical hybrid for conceptual queries), global_search (cross-vault exact-match grep), outline (file or directory structure tree), read (full file or single section by heading), frontmatter_get (parse YAML frontmatter), bulk_read (read multiple files/headings in one call), backlinks (find all notes linking to a given path).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
pathNo
queryNo
maxChunksNo
headingNo
headingDepthNo
directoryNoFilter search results to a specific directory or path prefix. Example: 'projects/active/'
itemsNoFor bulk_read: array of files to read, each with optional heading to extract.
Behavior2/5

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

With no annotations provided, the description carries full burden but only lists actions without disclosing behavioral traits like idempotency, rate limits, permissions, or side effects. For example, 'search' is mentioned but not whether it modifies data or requires authentication.

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

Conciseness2/5

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

The description is densely packed into a single paragraph with many actions and details, lacking clear structure. Bullet points would improve readability without losing information.

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

Completeness2/5

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

Given the tool's complexity (8 parameters, 8 actions) and no output schema, the description is incomplete. It does not specify which parameters are required for each action, leaving the agent without crucial usage details.

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

Parameters2/5

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

Schema coverage is only 25%, and the description does not add meaning to most parameters. It lists actions but fails to explain parameters like 'maxChunks' or 'heading', which are critical for correct invocation.

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 the tool's purpose as 'Read and search markdown notes' and enumerates specific actions (search, read, etc.), distinguishing it from siblings like 'edit' or 'system'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description lists actions but does not explain which action is appropriate for different scenarios or compare to sibling tools.

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/wirux/mcp-markdown-vault'

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