Engram Obsidian Memory Sync

Append to Note

append_to_note

Add text to the end of a note. Existing text is kept. If the note does not exist it is created with a # <name> title line first. Use for logs, journals and running lists. Set position to start to insert at the top (after any frontmatter) instead. To change existing text use edit_note. To replace the whole note use write_note.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Full path for the note
`text`	Yes	Text to append
`position`	No	end (default) appends; start inserts at the top, after any frontmatter	end
`vault_id`	No	Target vault: its name (e.g. "Engram") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`created`	Yes	true when the note did not exist and was created

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / position

Added value: +{
+  "default": "end",
+  "description": "end (default) appends; start inserts at the top, after any frontmatter",
+  "enum": [
+    "end",
+    "start"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / vault_id / description

Previous value: -"Target vault — its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault — the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."New value: +"Target vault: its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the mutation/idempotency/destructiveness profile, so the bar is lower. The description adds genuinely non-obvious context beyond them: it creates the note with a title line if missing, preserves existing text, and inserts position=start after any frontmatter rather than at the very top.

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?

Front-loads the core action and keeps each sentence purposeful, but the position guidance and the alternatives are spread across several short sentences with mild overlap between the opening line and the position=start sentence.

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?

For a 4-param mutation tool with an output schema, the description covers creation semantics, insertion position, and sibling routing. It leaves return-value detail to the output schema, which is acceptable, though the vault_id multi-vault requirement is only implied.

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 coverage is 100%, so parameters like path, text, position and vault_id are already fully documented. The description's position=start note ('after any frontmatter') roughly restates the enum description; it adds little beyond the schema.

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?

States a specific verb (add/append) and resource (note end), plus the non-obvious auto-create behavior. Explicitly distinguishes itself from edit_note and write_note, so an agent can route correctly without opening sibling schemas.

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?

Gives concrete use cases (logs, journals, running lists), names both alternatives (edit_note for changing text, write_note for replacing the whole note), and explains the position=start variant. Nothing is left to inference.

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

All Engram Obsidian Memory Sync tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.