You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
README.md read-tools list is missing get_vault_tree, while the tool is implemented and exposed in MCP.
docs/01-overview.md still has Read-first tools (planned): TBD and Write tools (planned): TBD even though the current tool surface is already documented as implemented in the same file and in docs/reference/mcp-tools.md.
docs/03-plan.md is still valid as the repo TODO tracker, but remaining items are spread across sections and not easy to scan as a current backlog snapshot.
Current docs should make a clear boundary between “implemented now” and “remaining backlog” to avoid drift/confusion.
Suggested fix (optional)
Add get_vault_tree to the read-tools list in README.md.
Replace TBD planned placeholders in docs/01-overview.md with explicit status text aligned to current implementation.
Keep docs/03-plan.md (per AGENTS guidance) and add a short “remaining backlog” summary near the top with currently open items:
Doc location
README.mddocs/01-overview.mddocs/03-plan.mdWhat’s wrong / missing?
README.mdread-tools list is missingget_vault_tree, while the tool is implemented and exposed in MCP.docs/01-overview.mdstill hasRead-first tools (planned): TBDandWrite tools (planned): TBDeven though the current tool surface is already documented as implemented in the same file and indocs/reference/mcp-tools.md.docs/03-plan.mdis still valid as the repo TODO tracker, but remaining items are spread across sections and not easy to scan as a current backlog snapshot.Suggested fix (optional)
get_vault_treeto the read-tools list inREADME.md.TBDplanned placeholders indocs/01-overview.mdwith explicit status text aligned to current implementation.docs/03-plan.md(per AGENTS guidance) and add a short “remaining backlog” summary near the top with currently open items:frontmatter_validateread_notepagination token/perf follow-ups