Skip to main content
Glama
pvliesdonk

markdown-vault-mcp

by pvliesdonk

Reindex Vault

reindex
Idempotent

Update the index after external file modifications. Only call after changes by text editor, sync tool, or other process; internal updates index automatically.

Instructions

Submit an incremental reindex job to the writer.

Only needed when files are modified outside this server — for example, by a text editor, a sync tool, or another process writing directly to the vault directory. Do NOT call this after using 'write', 'edit', 'delete', or 'rename' — those tools update the index immediately as part of the operation.

To rebuild all embeddings from scratch (e.g. after changing the embedding model), use 'build_embeddings' with force=True.

Returns: Dict with status: "queued". The reindex runs asynchronously on the writer thread. Poll get_index_status for completion:

- ``status == "queryable"`` AND ``queue_depth == 0`` AND
  ``in_flight is None`` → reindex completed.
- ``last_reindex_error`` not ``None`` → the most recent async
  reindex failed on the writer thread; the value is the
  stringified exception.  Operators can re-run ``reindex`` to
  retry; a subsequent successful run clears the field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable behavioral details: asynchronous execution on writer thread, return format with 'queued' status, polling instructions via get_index_status, and error handling. No contradiction with annotations.

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?

Well-structured with three paragraphs: purpose, usage guidance, and return value/behavior. Each sentence adds value; no fluff. Minor improvement could be more concise, but it's effective.

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?

Given no parameters and an existing output schema (not shown but stated present), the description fully covers when/why to use, how it behaves asynchronously, how to monitor completion, and error handling. It also references a sibling tool for an alternative use case.

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?

No parameters, so schema coverage is 100%. The description does not need to explain parameters but instead explains return values and asynchronous behavior, which is sufficient.

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 submits an incremental reindex job and specifies exactly when it is needed (files modified outside the server). It distinguishes itself from sibling tools like 'build_embeddings' and explicitly says not to call after write/edit/delete/rename.

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?

Provides explicit guidance on when to use (external modifications) and when not to use (after tool operations that already update the index). Also recommends an alternative tool ('build_embeddings') for full rebuild.

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