Note Context
get_contextRead-onlyIdempotent
Consolidates a document's metadata, backlinks, outlinks, similar notes, folder peers, and tags into one call. Replace multiple separate queries to understand a note's context in the vault.
Instructions
Get a consolidated context dossier for a document.
Replaces separate calls to 'get_backlinks', 'get_outlinks', and 'get_similar' when you need more than one.
Returns everything useful about a note in one call: its metadata, backlinks (documents that link to it), outlinks (documents it links to), semantically similar notes, other notes in the same folder, and indexed frontmatter tags. Use this instead of making 4-5 separate tool calls when you need a full picture of a note's place in the vault.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Relative path of the document (e.g. "notes/topic.md"). Case-sensitive. | |
| link_limit | No | Maximum number of backlinks and outlinks to include each (default 10). | |
| similar_limit | No | Maximum number of similar notes to include (default 5). Pass 0 to skip the similarity lookup — do this when 'stats' shows semantic_search_available=False (embeddings are not configured). | |
| wait_for_pending_writes | No | When True, wait until your recent write/edit/delete/rename operations have been applied to the index before answering, so the results reflect those changes. Use it right after modifying notes when this read must see them (e.g. right after a write/edit/delete/rename whose effect this read should reflect). Default False answers immediately from the current index — almost always already up to date; inspect the response's ``_meta.index_stale`` field to tell whether a write was still in flight. Bounded by a server timeout (default 60s); on timeout it answers from the current index rather than waiting longer. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||