Skip to main content
Glama
aliasunder

Vault Cortex Obsidian MCP Server

by aliasunder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Memory

vault_get_memory
Read-onlyIdempotent

Retrieve user preferences, principles, and opinions from structured memory files, with optional filtering by section or date for targeted context.

Instructions

Read semantic memory from About Me/ files. These are structured memory files containing dated bullet entries organized under H2 headings. With file: single file content. With file+section: just that H2 section's entries. No args: all files concatenated (frontmatter stripped) — can be large. Returns empty string when no memory files exist yet.

With file+on_or_after: returns structured JSON entries dated on or after the boundary date (inclusive), in document order (newest first when the file lists new entries at the top, the default). Add section to scope to one H2 section; omit it to read every H2 section's entries in the file, each keeping its section attribution. Designed for reconciliation consumers that know a boundary date and need deterministic chronological coverage without re-parsing the section.

Example: vault_get_memory({ file: "Principles", section: "Decision heuristics (newest first)" }) Example: vault_get_memory({ file: "Opinions", section: "Code patterns", on_or_after: "2026-09-01" }) Example: vault_get_memory({ file: "Opinions", on_or_after: "2026-09-01" }) — every section's entries since the date

When to use: Reading user preferences, principles, opinions, or other persistent context stored in About Me/ files. Call vault_list_memory_files first to discover valid file and section names. Use on_or_after when you need entries from a known date forward (e.g. reconciliation boundaries). Prefer vault_read_note for reading non-memory notes.

Errors:

  • "section requires a file" — section was provided without file; pass both or just file

  • "on_or_after requires a file" — on_or_after needs a file to scope the filter

  • "memory file not found" — file does not exist in About Me/; call vault_list_memory_files to discover valid names

  • "memory file must not start with a dot" — a dot-prefixed name would be a hidden file; memory files are always visible notes

  • "section not found: …" — no H2 heading matches; the error lists the file's available sections

  • "date must be a real ISO calendar date" — on_or_after must be a valid YYYY-MM-DD date

Returns: Without on_or_after, raw markdown text. With on_or_after, JSON { entries, total, on_or_after } where each entry is { file, section, date, text } — text is the full raw entry markdown (bullet + continuation lines, wikilinks intact), same shape as vault_memory_recall entries. An empty match returns { entries: [], total: 0 }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoMemory file name without .md (e.g. "Principles", "Opinions")
sectionNoH2 section heading (e.g. "Decision heuristics (newest first)"). Matched case-insensitively, with or without the "(newest first)" suffix. Omit to read the whole file (with on_or_after, every H2 section's entries). Call vault_list_memory_files first to discover valid names.
on_or_afterNoInclusive date filter (YYYY-MM-DD). When provided with file, returns structured JSON entries dated on or after this date instead of raw markdown. Requires a file; add section to scope to one H2 section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.54.1
    • changedInput schema / properties / on_or_after / description
      Previous value: -"Inclusive date filter (YYYY-MM-DD). When provided with file and section, returns structured JSON entries dated on or after this date instead of raw markdown. Requires both file and section."New value: +"Inclusive date filter (YYYY-MM-DD). When provided with file, returns structured JSON entries dated on or after this date instead of raw markdown. Requires a file; add section to scope to one H2 section."
    • changedInput schema / properties / section / description
      Previous value: -"H2 section heading (e.g. \"Decision heuristics (newest first)\"). Matched case-insensitively, with or without the \"(newest first)\" suffix. Call vault_list_memory_files first to discover valid names."New value: +"H2 section heading (e.g. \"Decision heuristics (newest first)\"). Matched case-insensitively, with or without the \"(newest first)\" suffix. Omit to read the whole file (with on_or_after, every H2 section's entries). Call vault_list_memory_files first to discover valid names."
  2. Changed1 schema field changedv0.53.0
    • addedInput schema / properties / on_or_after
      Added value: +{
+  "description": "Inclusive date filter (YYYY-MM-DD). When provided with file and section, returns structured JSON entries dated on or after this date instead of raw markdown. Requires both file and section.",
+  "minLength": 1,
+  "type": "string"
+}
  3. Addedv0.32.1
  4. Removedv0.32.0
  5. Changed2 schema fields changedv0.22.1
    • addedInput schema / properties / file / minLength
      Added value: +1
    • addedInput schema / properties / section / minLength
      Added value: +1
  6. Changed1 schema field changedv0.19.2
    • changedInput schema / properties / section / description
      Previous value: -"H2 section heading (e.g. \"Decision heuristics (newest first)\"). Call vault_list_memory_files first to discover valid names."New value: +"H2 section heading (e.g. \"Decision heuristics (newest first)\"). Matched case-insensitively, with or without the \"(newest first)\" suffix. Call vault_list_memory_files first to discover valid names."
  7. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive; the description goes well beyond by disclosing that no-args output can be large, returns an empty string when no memory files exist, switches output to JSON when on_or_after is used, defines document order semantics, and lists all error conditions.

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?

Long, but every block earns its place: core behavior, examples, when-to-use, errors, and return formats. The use of labeled sections makes it skimmable, and the most decision-relevant behavior (modes and outputs) appears first.

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?

Despite having no output schema, the description fully specifies return shapes for both markdown and JSON modes, empty-file and empty-match behavior, prerequisites, and error messages. An agent has everything needed to invoke it correctly without consulting external documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes all three parameters at 100% coverage, the description adds real value: concrete call examples, conditional output-format changes, case-insensitive section matching with optional '(newest first)' suffix, and the file-scoping requirement for on_or_after. This significantly exceeds the baseline.

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?

Opens with a specific verb and resource: 'Read semantic memory from About Me/ files.' It then enumerates distinct retrieval modes (whole collection, one file, one H2 section, dated filter), which clearly separates it from vault_read_note and vault_memory_recall.

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?

Provides an explicit 'When to use' section stating this tool is for user preferences/principles/opinions, directs the agent to call vault_list_memory_files first to discover valid names, and explicitly says to prefer vault_read_note for non-memory notes. This is model routing guidance.

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

Deploy Server

Other Tools