Skip to main content
Glama
Sign In
obsidian-mcp

obsidian-mcp

by thoreinstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

obsidian_set_vault

Set the default Obsidian vault path for this session so note search and management target the correct local vault.

Instructions

Set the default Obsidian vault path for this session.

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": {
      "path": "<path>"
    },
    "name": "obsidian_set_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the Obsidian vault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says the vault applies 'for this session,' which is useful scoping context, but never states whether the path must exist, whether invalid paths error, whether this persists across sessions, or what happens to previously listed notes.

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?

A single, front-loaded sentence with zero waste. The session-scoping constraint is stated immediately and nothing is redundant.

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

Completeness2/5

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

For a state-setting tool with no annotations and no output schema, the description should cover prerequisites (does the vault need to exist?) and side effects (does this affect all subsequent Obsidian calls?). It covers only the bare minimum.

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?

Schema coverage is 100%, so the sole 'path' parameter is fully documented as an absolute path in the schema. The description adds no syntax or format detail beyond that, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (set) and resource (default Obsidian vault path) scoped to the session. It's clear what the tool configures, though it doesn't differentiate itself from other configuration siblings or explain how this state interacts with the rest of the Obsidian toolset.

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

Usage Guidelines2/5

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

No guidance on when to call this versus alternatives. With a catalog of 17 sibling tools, the description doesn't tell the agent when this setup step is required or how the vault default affects subsequent operations.

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