markdown-vault-mcp

Append to Note

append

Add text to the end of a Markdown note without reading the file first, saving context and avoiding unnecessary edits. Ideal for logs, journal entries, or checklist items.

Instructions

Append text to the end of an existing .md note without reading it.

The cheapest way to add content at the end of a note (log entries, journal additions, checklist items): unlike 'edit', no prior 'read' is needed, so the existing note content never enters the context. Prefer this over 'edit' whenever the change is purely additive at the end of the note.

A newline is inserted between the existing content and the appended text when the file does not already end with one, so the appended text starts on its own line. Include leading blank lines or heading markers in 'content' yourself if you want a separating paragraph or section. The index refresh is queued; no reindex is needed.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Relative path to the document (e.g. "Journal/2026.md").
`content`	Yes	Text to append (must be non-empty). Added at the end of the file, after frontmatter and all existing content.
`if_match`	No	Optional etag obtained from a previous 'read' call. When provided, the append only proceeds if the file has not been modified since that read (optimistic concurrency). Omit to append unconditionally.
`create_if_missing`	No	When true, a missing note is created with 'content' as its body instead of failing. Default false — a typo in 'path' fails loudly rather than silently creating a new note.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv4.0.0Aug 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already set readOnlyHint=false and destructiveHint=false; description adds non-obvious behaviors: automatic newline insertion only when missing, queued index refresh with no reindex needed, and no read required. No contradictory statements.

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?

Four short sentences, each earns its place: purpose first, usage guidance second, newline detail third, index behavior last. No filler or repeated schema content.

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?

For a 4-param tool with full schema detail and an output schema, the description covers the behavioral decisions an agent needs: when to choose it, what happens to newlines, and post-append index state. No significant gap remains.

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 has 100% coverage, so baseline is 3; description adds practical meaning by explaining the automatic newline behavior and telling the caller to include blank lines/heading markers for separation. It does not elaborate every parameter, but the schema already does.

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?

Description opens with 'Append text to the end of an existing .md note without reading it', giving a specific verb, resource, and scope. It explicitly contrasts with 'edit', making sibling differentiation immediate.

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?

States the exact condition for use—'purely additive at the end of the note'—and tells the agent to prefer this over 'edit'. Also notes that no prior 'read' is needed, which is the key cost/context benefit.

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