Skip to main content
Glama
bezata

kObsidian MCP

by bezata

Select Active Vault

vault.select

Set the active vault for subsequent filesystem operations by id, name, or path, ensuring file tools target the correct Obsidian vault.

Instructions

Set the session-active vault for subsequent filesystem tool calls. Identify the target by EXACTLY ONE of id (stable id from vault.list), name (case-insensitive match), or path (absolute directory path — need not appear in vault.list; lets the LLM point at a fresh/empty vault to initialise). Precedence chain becomes: per-call vaultPath argument (highest) → this session selection → OBSIDIAN_VAULT_PATH → error. Explicit vaultPath arguments on individual tool calls always override this selection. Respects KOBSIDIAN_VAULT_ALLOW / KOBSIDIAN_VAULT_DENY operator gating (though OBSIDIAN_VAULT_PATH is never filtered). Does NOT change which vault the live Obsidian process has open — workspace.* and commands.* tools remain tied to OBSIDIAN_API_URL. HTTP deployments: this server shares the selection across HTTP clients, so concurrent multi-client HTTP setups should pass vaultPath per call instead.

Examples:

Example 1 — Switch to the vault named 'Work':

{
  "name": "Work"
}

Example 2 — Select by id from vault.list:

{
  "id": "58f115bd2c2febd2"
}

Example 3 — Point at an ad-hoc path (e.g. a fresh vault to initialise):

{
  "path": "/Users/alice/FreshVault"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoVault id returned by `vault.list`. Mutually exclusive with `name` and `path`.
nameNoCase-insensitive vault name match against `vault.list`. Mutually exclusive with `id` and `path`.
pathNoAbsolute vault directory path. Need not appear in `vault.list` — accepting an ad-hoc path lets the LLM point at a fresh vault. Must exist and be a directory. Mutually exclusive with `id` and `name`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeYesA single vault entry returned by `vault.list` and `vault.current.active`.
targetYes
changedYes
summaryYes
previousYesThe previously-selected vault, or null if none was selected.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are minimal (all false), so the description carries the full burden and delivers richly. It discloses the state-mutating nature (sets session selection), the precedence chain behavior, that OBSIDIAN_VAULT_PATH is never filtered by KOBSIDIAN_VAULT_ALLOW/DENY gating, the non-effect on the live Obsidian process, and the shared-selection caveat for HTTP deployments. No contradiction with annotations — readOnlyHint=false aligns with this being a state-setter.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, then scoping and behavioral notes follow, then examples. The description is long but information-dense — the precedence, gating, workspace-scope, and HTTP notes each earn their sentences. The three concrete JSON examples add real clarity. Slightly verbose for a simple setter, but nothing is wasted.

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?

Complete coverage for a targeting/selection tool: purpose, identifier selection rules, precedence, env-var interaction, operator-gating behavior, scope exclusions, HTTP deployment caveat, and worked examples. Combined with the output schema, an agent has everything needed to invoke this correctly without further lookup.

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?

Schema coverage is 100% and each parameter is already documented with mutual-exclusivity. The description adds genuine value beyond the schema: name matching is case-insensitive, path need not appear in vault.list (enabling fresh-vault initialization), and the interaction of each identifier with the precedence chain. It enriches but doesn't merely duplicate 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 opens with a specific verb+resource: 'Set the session-active vault for subsequent filesystem tool calls.' It clearly differentiates from sibling vault tools (vault.list, vault.current, vault.reset) by explaining the selection mechanism with three distinct identifiers. The sibling distinction is precisely stated.

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?

Explicit guidance on when to use each parameter: `id` for stable lookups, `name` for case-insensitive matching, `path` for ad-hoc/fresh vaults to initialize. The precedence chain is fully documented (per-call vaultPath > session selection > OBSIDIAN_VAULT_PATH), and it specifies exclusions — workspace.*/commands.* tools remain tied to OBSIDIAN_API_URL, and HTTP deployments should pass vaultPath per call. Nothing is left to inference.

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

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