Engram Obsidian Memory Sync

Delete Note

delete_note

DestructiveIdempotent

Delete a note from the knowledge base. The deletion will sync to all connected Obsidian devices.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Path of the note to delete
`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
`deleted`	Yes	false when no note existed at that path

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate destructive and non-read-only behavior, so the description's addition that 'deletion will sync to all connected Obsidian devices' adds useful behavioral context beyond the structured data. It does not contradict the annotations.

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?

The description is two concise sentences with no filler. The core action is front-loaded, and the additional sync behavior is stated in a single efficient clause.

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 low-complexity delete operation with a full parameter schema, an output schema, and destructive/idempotent annotations, the description covers the essential behavior. The sync side effect is the only notable behavioral disclosure needed, and it is present.

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 description coverage is 100%, with both path and vault_id already documented in detail. The description itself adds no parameter-specific meaning, so it relies on the schema, which is adequate and earns the baseline score.

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 states a specific action ('Delete a note') and a clear resource ('from the knowledge base'), distinguishing it from sibling tools like delete_folder. The verb and object are unambiguous, leaving no doubt about the tool's function.

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 makes the tool's purpose clear but provides no explicit guidance on when to prefer it over alternatives or when not to use it. There is no mention of delete_folder for directories or any exclusions, so usage is implied rather than stated.

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.