Hybrid retrieval over the read-only index: fuses SQLite FTS5 lexical search with sqlite-vec dense (semantic) ranking via reciprocal-rank fusion, degrading gracefully to lexical-only when embeddings are unavailable. Returns ranked hits (source markdown path, heading, fused score, matched channels, a snippet, and git recency) so an agent can recall facts, notes, and decisions from the vault by a natural-language query. k caps the number of hits (default 10).

Hybrid (lexical + dense) search over the read-only index: functionally identical to search, exposed under this namespaced alias for clients that auto-prefix tool names with the server id. Fuses FTS5 lexical and sqlite-vec semantic ranking via reciprocal-rank fusion (degrading to lexical-only without embeddings) and returns the same ranked hits (path, heading, score, channels, snippet, git recency). Prefer search; reach for this alias only when your client requires the prefixed name. k caps the number of hits (default 10).

Pages reachable from a page via body wikilinks (in+out edges).

Entity resolution: resolve a name to an existing page path (gbrain's get role), or null if ambiguous/missing. The caller strips .md (use slug) to form a wikilink target.

Thinking-mode: related notes + Socratic prompts + related-but-not-yet-linked pairs. Pass the active note's path to exclude it from its own results. Never writes (wrote: false).

Discover the vault's folder taxonomy + writable locations before placing a note: child folders under root (drill-down) to depth levels, each with its writability, protected reason, and recursive note count, plus direct root-local AGENTS.md/CLAUDE.md guidance when present. Read-only; the writable flag matches what commit_note accepts. Narrow root to drill deeper when truncated is true.

Read the full markdown content of a single note by its repo-relative path (typically a path returned by search, resolve, or build_context). Read-only and bounded to indexed notes: a path that is not a committed note in the vault returns found: false with content: null, never an out-of-vault or traversal read. Use it to fetch a note's body after locating it with the other read tools.