Skip to main content
Glama
Vault Cortex Obsidian MCP Server

Vault Cortex Obsidian MCP Server

Recent Notes

vault_recent_notes
Read-onlyIdempotent

List recently modified or created Obsidian notes sorted by timestamp to catch up on vault changes, find recent work, or reorient after a break.

Instructions

List recently modified or created notes, sorted by timestamp — a time-ordered window into the vault, not a date-range filter.

Example: vault_recent_notes({ limit: 10 }) Example: vault_recent_notes({ sort_by: "created", limit: 5 })

When to use: Catching up on vault changes, finding recent work, or orienting after a break. Prefer vault_search for content-based discovery, including a text query limited to a date range (its created and modified filters). Prefer vault_search_by_folder for browsing a specific folder.

Parameters:

  • sort_by "modified" uses filesystem mtime. Any file write counts (content edits, property changes, sync touches), so recently-synced notes appear recent even without user edits.

  • sort_by "created" uses the created property; notes where it is missing or not an ISO date sort after every dated note, so a small limit can leave them out — use "modified" to see them.

Behavior: Results can lag a file change by a few seconds.

Errors:

  • An empty vault returns an empty array, not an error.

  • "[SqliteError]: …" / "[IndexIntegrityError]: …" — the index failed, not the call; the message says what to do

Returns: JSON array of note metadata: path, title (the title property; file name without .md when missing or not text), tags (the tags property; vault_update_properties edits it), body_tags (#tags in the note's text, one per spelling; vault_replace_in_note edits them; absent when none), related ([] when missing), folder (top-level, "" at the root), type (null when missing or not text), created (null when missing or not an ISO date), modified (ISO 8601 file time), bytes (on-disk size), and when present leading_callout (the opening callout, { type, title, body }) and additional_properties (every property but title, type, created, related and tags). Newest first by the sort_by timestamp.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vault_recent_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
sort_byNoTimestamp to sort by (default "modified")modified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.56.3
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20, no upper cap)"New value: +"Max results (default 20)"
  2. Changed1 schema field changedv0.55.4
    • changedInput schema / properties / sort_by / description
      Previous value: -"Timestamp to sort by, newest first (default \"modified\")"New value: +"Timestamp to sort by (default \"modified\")"
  3. Changed1 schema field changedv0.54.16
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed1 schema field changedv0.54.13
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort order (default \"modified\")"New value: +"Timestamp to sort by, newest first (default \"modified\")"
  5. Changed5 schema fields changedv0.50.0
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / sort_by / default
      Added value: +"modified"
  6. Addedv0.32.1
  7. Removedv0.32.0
  8. Changed2 schema fields changedv0.23.6
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20, no upper cap). Example: limit: 5 returns the top 5 by chosen timestamp."New value: +"Max results (default 20, no upper cap)"
    • changedInput schema / properties / sort_by / description
      Previous value: -"\"created\" or \"modified\" (default). \"modified\" uses filesystem mtime (any write, including sync, updates it). \"created\" uses the frontmatter created property — notes without it sort last; pair with a higher limit to include them."New value: +"Sort order (default \"modified\")"
  9. Changed2 schema fields changedv0.23.5
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 20). When sorting by created, notes without a created property sort last and may fall outside a small limit."New value: +"Max results (default 20, no upper cap). Example: limit: 5 returns the top 5 by chosen timestamp."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property sort to the bottom of created-sorted results — with a small limit they may not appear at all."New value: +"\"created\" or \"modified\" (default). \"modified\" uses filesystem mtime (any write, including sync, updates it). \"created\" uses the frontmatter created property — notes without it sort last; pair with a higher limit to include them."
  10. Changed2 schema fields changedv0.23.3
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 20)"New value: +"Max results to return (default 20). When sorting by created, notes without a created property sort last and may fall outside a small limit."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property are excluded from created-sorted results."New value: +"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property sort to the bottom of created-sorted results — with a small limit they may not appear at all."
  11. Changed2 schema fields changedv0.22.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20)"New value: +"Max results to return (default 20)"
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort field: \"created\" or \"modified\" (default \"modified\")"New value: +"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property are excluded from created-sorted results."
  12. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description's job is deeper context — and it delivers: mtime semantics where any file write or sync touch counts, the created-property ordering quirk that pushes undated notes to the end, a few-second index lag, empty-vault behavior, and how index error prefixes should be interpreted. This is behavior an agent could not infer from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a one-line purpose and scoped with labeled sections (Parameters, Behavior, Errors, Returns), which makes it skimmable despite its length. The two example invocations are borderline redundant with the schema defaults, keeping it just short of a 5.

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?

No output schema exists, so the description carries the return contract — it enumerates every field, explains null and empty-string cases, and clarifies that body_tags and tags are distinct. Errors, lag, and default ordering are all covered, leaving nothing an agent needs in order to call it correctly.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine semantics beyond the schema: what timestamp source each sort_by value actually reads and the concrete failure mode of sorting by "created" with a small limit. That directly changes how an agent would choose a sort key.

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 and resource ("List recently modified or created notes") plus the sorting contract, and immediately distinguishes itself from a date-range filter. Sibling differentiation is explicit later (vault_search, vault_search_by_folder), so an agent can pick this tool without opening another schema.

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 a named "When to use" scenario set (catching up, finding recent work, orienting after a break) and explicitly routes to two alternatives with the conditions that select them — content discovery and date-range queries go to vault_search, folder browsing to vault_search_by_folder. Exclusions are stated, not implied.

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