Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_active_vault

Sets which Obsidian vault will be used for all subsequent note operations. Specify the vault name to switch context and enable targeted access to your notes.

Instructions

Set the active vault for subsequent operations

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vault": "<vault>"
    },
    "name": "set_active_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultYesName of the vault to set as active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it sets state but does not disclose persistence, failure modes, or whether the vault must already be registered. For a state-changing operation, this is insufficient detail.

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?

The description is a single sentence with no fluff, clearly front-loaded with the verb and resource. It efficiently states what the tool does and its purpose without wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the description omits important context such as whether the setting persists, what happens on invalid input, and how the vault name relates to list_vaults. With no output schema or annotations, more behavioral context would make it more complete.

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

Parameters3/5

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

The input schema fully documents the 'vault' parameter, so the description does not need to add much. It does not add syntax or source details beyond the schema, but schema coverage is 100%, so the baseline of 3 is appropriate.

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 identifies the verb 'set' and the resource 'active vault', and explains its purpose for subsequent operations. This distinguishes it from sibling tools like list_vaults and register_vault, which manage vaults rather than set the current one.

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

Usage Guidelines3/5

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

The phrase 'for subsequent operations' provides some context, implying that this tool should be used before other operations that require a vault context. However, there is no explicit guidance on when to use this tool vs alternatives, nor any mention of prerequisites like having a registered vault.

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

Deploy Server

Other Tools