vault-engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vault_inspect_graphB | [KNOWLEDGE GRAPH INSPECTOR] Pindai seluruh vault Obsidian dan dapatkan metrik jaringan pengetahuan: Total catatan (nodes), total relasi wikilink (edges), densitas graf, central hubs (catatan paling dirujuk), orphan notes (catatan terisolasi tanpa tautan), dan jumlah broken links. |
| vault_lint_noteB | [VAULT LINTER] Pindai satu catatan terhadap aturan integritas vault Otak-Koding:
|
| vault_get_backlinksB | [BACKLINK NAVIGATOR] Dapatkan seluruh catatan yang merujuk (inbound links) dan dirujuk oleh (outbound links) satu catatan tertentu. Juga mendeteksi apakah ada broken wikilink di dalam catatan tersebut. |
| vault_find_broken_linksB | [BROKEN LINK DETECTOR] Temukan seluruh tautan wikilink [[...]] yang putus di seluruh vault (merujuk ke berkas/catatan yang belum pernah dibuat). |
| vault_searchB | [FAST VAULT SEARCH] Cari catatan di vault berdasarkan kata kunci judul/isi, saringan tag (misal: 'akuntansi'), atau saringan kategori direktori (misal: '10-Rekayasa-ERP' atau 'backend'). |
| vault_scaffold_noteC | [NOTE SCAFFOLDER] Hasilkan templat catatan Markdown baru yang 100% mematuhi standar vault Otak-Koding: Nama berkas otomatis kebab-case, frontmatter YAML lengkap 6 kunci wajib, template invarian uji, dan baris penutup. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct primary purpose (graph metrics, search, lint, backlinks, scaffolding), but broken-link checking appears in four tools (inspect_graph counts them, find_broken_links lists them, get_backlinks and lint_note also report them), creating some selection ambiguity. The description headers ([BROKEN LINK DETECTOR], [VAULT LINTER], etc.) help an agent choose, but an agent may still pick the wrong tool when it just wants broken links.
All names share a consistent vault_ prefix and use snake_case with verb_noun structure (inspect_graph, find_broken_links, lint_note, get_backlinks, scaffold_note). The only minor deviation is vault_search, which lacks a noun component.
Six tools is a well-scoped set for a vault analysis/linting server, and each tool earns its place. It is on the lean side given that the surface is read/analyze-only with no mutation tools.
The analysis surface (search, graph metrics, lint, backlinks, broken links, scaffolding) is reasonably covered, but there is no tool to read a full note's content, write/create a note from the scaffold, update frontmatter, rename/move a note, or fix broken links. These gaps mean an agent can diagnose issues but cannot remediate them, and vault_lint_note needs content that no tool can fetch.