Skip to main content
Glama
bezata

kObsidian MCP

Reset Active Vault Selection

vault.reset
Idempotent

Clear the session-selected vault to revert to the default OBSIDIAN_VAULT_PATH. Use when done with a scratch vault to restore the default vault path.

Instructions

Clear the session-selected vault so the precedence chain falls back to OBSIDIAN_VAULT_PATH. Use this to signal 'I'm done with the scratch vault, go back to the default'. Idempotent — running on an already-cleared session is a no-op that reports changed: false. Does not change per-call vaultPath behaviour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYes
targetYes
summaryYes
previousYes

Implementation Reference

  • The handler function for vault.reset. It parses args (none), reads the current active vault from context.session.activeVault, sets it to null, and returns whether the state changed, the target vault path, a summary message, and the previous vault record.
    handler: async (context, rawArgs) => {
      vaultResetArgsSchema.parse(rawArgs) as VaultResetArgs;
      const previous = context.session.activeVault;
      context.session.activeVault = null;
      return {
        changed: previous !== null,
        target: context.env.OBSIDIAN_VAULT_PATH ?? "",
        summary: previous
          ? `Active vault selection cleared (was "${previous.name}")`
          : "No active vault selection to clear",
        previous,
      };
    },
  • Input schema for vault.reset: an empty object (no arguments required).
    export const vaultResetArgsSchema = z
      .object({})
      .strict()
      .describe("Arguments for `vault.reset` (none).");
    export type VaultResetArgs = z.input<typeof vaultResetArgsSchema>;
  • Output schema for vault.reset: returns changed (boolean), target (string), summary (string), and previous (nullable vault record).
    export const vaultResetOutputSchema = z
      .object({
        changed: z.boolean(),
        target: z.string(),
        summary: z.string(),
        previous: vaultRecordSchema.nullable(),
      })
      .describe("Return shape of `vault.reset`.");
  • vault.reset is registered as a ToolDefinition in the vaultTools array exported from src/server/tools/vaults.ts. The array is imported into the central tool registry at src/server/registry.ts.
      vaultResetArgsSchema,
      vaultResetOutputSchema,
      vaultSelectArgsSchema,
      vaultSelectOutputSchema,
    } from "../../schema/vaults.js";
  • The vaultTools array (containing vault.reset) is imported and spread into the central toolRegistry at src/server/registry.ts.
    import { vaultTools } from "./tools/vaults.js";
    import { wikiTools } from "./tools/wiki.js";
    
    export const toolRegistry: ToolDefinition[] = [
      ...vaultTools,
Behavior4/5

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

Adds value beyond annotations by noting idempotency reports 'changed: false' and that per-call vaultPath is unaffected. Annotations already include idempotentHint=true, but description enriches with concrete behavior.

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?

Three sentences, no waste. Core action first, usage second, behavioral note third. Front-loaded and efficient.

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?

Given zero parameters and simple behavior, description covers purpose, usage, and safety. Output schema exists but not needed for completeness. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; schema coverage is 100%. Baseline 4 applies as description does not need to add parameter info. The description correctly explains tool function without referencing parameters.

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?

Description clearly states it clears the session-selected vault to fall back to the default. Uses strong verb 'reset' and specifies resource (active vault selection). Distinguishes from siblings like vault.select and vault.list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use: after finishing with a scratch vault. Implicitly contrasts with vault.select for picking a vault. Lacks explicit when-not but context with siblings provides clarity.

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