Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Current Active Vault

vault.current
Read-onlyIdempotent

Get the currently selected Obsidian vault for filesystem tools, showing the resolution reason (session-selected, env-default, or none) and the precedence chain, with a reminder when an Obsidian live instance is active.

Instructions

Return the vault that filesystem tools (notes., tags., dataview., blocks., canvas., kanban., marp., templates., tasks., links., wiki., stats.vault) would resolve to right now, plus the full precedence chain so the LLM can explain to the user why that vault was picked. reason is session-selected (vault.select was called), env-default (fell back to OBSIDIAN_VAULT_PATH), or none (nothing configured — tools will fail until vault.select or an env var is set). When OBSIDIAN_API_URL is configured, the response also carries an obsidianLiveInstance note reminding the caller that workspace. and commands.* tools target whichever vault the live Obsidian process has open, NOT the filesystem vault selected here. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeYesThe vault filesystem tools would resolve to right now. Null only when neither a session selection nor OBSIDIAN_VAULT_PATH is set.
reasonYesWhy `active` resolved this way: `session-selected` = set by vault.select; `env-default` = fell back to OBSIDIAN_VAULT_PATH; `none` = nothing is configured.
envDefaultYesThe OBSIDIAN_VAULT_PATH value at server startup, if any.
obsidianLiveInstanceNoPresent when OBSIDIAN_API_URL is configured. Explains that workspace.* and commands.* tools target the vault the live Obsidian process has open, independent of the filesystem vault selected here.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

The description goes beyond annotations by explaining the `reason` field values, the `obsidianLiveInstance` note, and clarifying that workspace/commands tools target a different vault. Fully discloses behavioral traits.

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?

The description is moderately long but well-structured, with the main purpose in the first sentence. Each sentence adds necessary context without redundancy.

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 no input parameters and the presence of an output schema, the description fully explains what the tool returns, including edge cases and interaction with other tools. Very complete.

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?

There are no parameters, and the schema coverage is 100% with a description stating no arguments. The description adds no parameter info, but baseline for zero params is 4.

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 that the tool returns the currently active vault and the precedence chain, with explicit mention of the `reason` field and `obsidianLiveInstance` note. It distinguishes itself from sibling tools like `vault.list` and `vault.select` by focusing on current active vault.

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?

The description implies usage when needing the current vault context, but does not explicitly say when not to use it or compare to alternatives. It mentions read-only and failure conditions, which aids appropriate use.

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