Engram Obsidian Memory Sync

Search Notes

search_notes

Read-onlyIdempotent

Search your personal knowledge base. Finds relevant notes using semantic search. Searches across ALL your vaults by default; pass vault_id to limit to one. Omit query to list the most recently updated notes instead. Pass similar_to with a note path, instead of query, to find notes like that one. Use when the user asks about their notes, vault, knowledge, or memory.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Retrieval mode (default hybrid). Use 'keyword' for exact terms, identifiers, code, or error strings; 'vector' for purely conceptual/semantic queries; 'hybrid' (default) blends both.	hybrid
`tags`	No	Optional list of tags to filter by
`type`	No	Optional frontmatter type to filter by (e.g. 'Playbook', 'Reference'); case-insensitive
`limit`	No	Maximum number of results (1-20, default 5)
`query`	No	Natural language search query. Omit, or leave empty, to list the most recently updated notes (filters then do not apply).
`folder`	No	Optional folder path to scope the search to (exact match)
`vault_id`	No	Optional: limit the search to a single vault, by name (e.g. "Engram") or UUID. Omit to search across ALL your vaults. Call list_vaults to see them.
`diversity`	No	Result diversity (0 = most relevant, default tuned per plan; 1 = most varied). Uses Maximal Marginal Relevance to reduce redundancy among results.
`similar_to`	No	Path of a note, e.g. "Projects/Alpha.md": return notes similar to it, using its stored embedding (no query needed). Do not combine with query. The note itself is excluded; filters still apply.
`created_after`	No	Only notes created at/after this ISO 8601 datetime (frontmatter created/date)
`updated_after`	No	Only notes updated at/after this ISO 8601 datetime (frontmatter timestamp/modified)
`created_before`	No	Only notes created at/before this ISO 8601 datetime
`updated_before`	No	Only notes updated at/before this ISO 8601 datetime

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / query / description

Previous value: -"Natural language search query"New value: +"Natural language search query. Omit, or leave empty, to list the most recently updated notes (filters then do not apply)."

addedInput schema / properties / similar_to

Added value: +{
+  "description": "Path of a note, e.g. \"Projects/Alpha.md\": return notes similar to it, using its stored embedding (no query needed). Do not combine with query. The note itself is excluded; filters still apply.",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

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

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds real behavioral context beyond them: default scope is ALL vaults unless vault_id is passed, filters are ignored in list mode, and similar_to excludes the source note. It omits ranking/pagination detail, but that is minor for a read-only search.

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 tight sentences, front-loaded with purpose then scoping then the two alternate invocation modes then the trigger. Every sentence carries information; no filler.

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 a rich 13-param schema with full coverage, an output schema, and safety annotations, the description covers the distinctions an agent actually needs (mode choice, listing fallback, similar_to path, vault scope) without redundantly restating schema text.

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, but the description adds cross-parameter relationships the per-field schema text does not state at a glance (query vs similar_to mutual exclusion, all-vaults default scope, filter suppression when query is omitted).

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+resource (semantic search over a personal knowledge base) and enumerates the three distinct invocation shapes: query, no-query listing of recent notes, and similar_to lookup. It also distinguishes itself from list_vaults by pointing there for vault discovery.

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?

Explicitly names the trigger condition ('when the user asks about their notes, vault, knowledge, or memory'), the alternative to query (omit it to list recent notes), and the substitute path (similar_to instead of query). 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.