Engram Obsidian Memory Sync

Create Note

create_note

Create a new note with automatic folder placement. If suggested_folder is omitted, the note is placed automatically. Never overwrites: fails if a note already exists at the resulting path.

Input Schema

Name	Required	Description
`title`	Yes	Title for the new note
`content`	Yes	Markdown content
`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.
`suggested_folder`	No	Only set when user explicitly named a folder

Output Schema

Name	Required	Description
`path`	Yes	Where the note landed; the server picks the folder
`search_note`	No	When search will see this change; use get_notes until then
`search_indexing_starts_in_seconds`	No	At least this many seconds until indexing starts; search can lag further. Use get_notes to read the note until search finds it

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedOutput schema / properties / search_indexing_starts_in_seconds

Added value: +{
+  "description": "At least this many seconds until indexing starts; search can lag further. Use get_notes to read the note until search finds it",
+  "type": "integer"
+}

addedOutput schema / properties / search_note

Added value: +{
+  "description": "When search will see this change; use get_notes until then",
+  "type": "string"
+}

Changed1 schema field changedSep 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields 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."

changedOutput schema / properties / path / description

Previous value: -"Where the note landed — the server picks the folder"New value: +"Where the note landed; the server picks the folder"

First observedSep 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely new behavior: automatic path resolution and a hard fail-on-existing rule, which is the key information an agent needs before retrying a failed call. It stops short of saying what the failure looks like or how the resulting path is chosen.

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?

Three short sentences, front-loaded with the core action, then the folder default, then the overwrite guarantee. No filler or restatement of the title.

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?

An output schema exists and vault scoping is fully documented in the schema, so the description only needs to cover the non-obvious create semantics, which it does. Minor gap: it doesn't clarify whether the automatic folder choice can be influenced or what happens when no folder matches.

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 coverage is 100%, so the baseline is 3; the description raises it slightly by explaining the consequence of omitting suggested_folder (automatic placement), which the schema does not state. The vault_id semantics are left entirely to a well-written schema entry, which is fine.

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?

States a specific verb and resource ('Create a new note') plus the non-obvious scope detail of automatic folder placement. It does not name the closest siblings (write_note, edit_note, append_to_note), so the agent must infer why create_note is preferred over write_note for a new file.

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?

The description gives a usable condition ('If suggested_folder is omitted, the note is placed automatically') and a failure condition ('fails if a note already exists at the resulting path'), but never says when to choose this over write_note or edit_note, which is the most likely selection mistake given the sibling list.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.