Skip to main content
Glama
bezata

kObsidian MCP

Rebuild Wiki Index

wiki.indexRebuild
DestructiveIdempotent

Regenerate the wiki index by scanning Sources, Concepts, and Entities folders. Replaces the entire index.md body — use after bulk page creation or when lint reports index mismatch.

Instructions

Regenerate wiki/index.md from a fresh scan of Sources/, Concepts/, and Entities/. Pages are grouped by category and sorted alphabetically; pass includeCounts:true to render counts on the section headings (e.g. ## Sources (12)). Idempotent and destructive — the existing index.md body is replaced wholesale, so any hand-edits there are lost. Use after bulk-creating pages outside the wiki tools, or as the cleanup step after wiki.lint reports indexMismatch. For incremental upkeep on a single source, prefer the proposedEdits returned by wiki.ingest instead.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Plain rebuild.:

{}

Example 2 — Rebuild with counts on each section heading.:

{
  "includeCounts": true
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeCountsNoWhen true, append per-category counts (e.g. `Sources (12)`) to each section heading. Defaults to false.
wikiRootNoPer-call wiki directory override.
vaultPathNoPer-call vault override.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
targetYesThe path or identifier the tool acted on.
summaryYesShort human-readable summary of what happened.
Behavior5/5

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

Annotations already provide destructiveHint and idempotentHint. The description adds context: the operation is destructive to hand-edits, idempotent, and operates on session-active vault unless vaultPath is given. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Efficiently structured: core action first, then details, usage guidelines, and examples. Every sentence serves a purpose, no fluff.

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?

Comprehensive coverage for a destructive, idempotent tool. Output schema exists, so return value detail is not needed. All necessary behavioral context is provided.

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%. The description adds meaning to 'includeCounts' with examples and explains precedence for vaultPath and wikiRoot, providing value beyond the schema.

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?

The description clearly states it regenerates 'wiki/index.md' from a fresh scan of specific directories, with grouping and sorting characteristics. This distinguishes it from siblings like wiki.ingest or wiki.lint.

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?

Explicitly mentions when to use (after bulk-creating pages, as cleanup after wiki.lint reports indexMismatch) and when to prefer an alternative (for incremental upkeep, use wiki.ingest's proposedEdits).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bezata/kObsidian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server