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

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

register_vault

Registers a new Obsidian vault with a name and absolute path, enabling the server to access and manage its notes.

Instructions

Register a new Obsidian vault with a name and path

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

Input Schema

NameRequiredDescriptionDefault
nameYesName to identify the vault
pathYesAbsolute path to the vault directory

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 only says 'Register a new Obsidian vault with a name and path,' but does not explain side effects, validation of the path, whether the vault becomes active, or return behavior. This is a significant gap for a mutating operation.

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, concise sentence that is front-loaded with the main verb and resource. It contains no filler or redundant information.

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 with two fully described parameters, but the lack of annotations and output schema means the description should explain what 'register' entails and what the caller can expect as a result. It does not, leaving the behavior somewhat ambiguous. Adequate but with clear gaps.

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 already provides 100% coverage with descriptions for both name and path. The description merely echoes 'name and path' without adding any additional meaning, so it does not go beyond the schema. Baseline 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 states the tool's function with a specific verb ('Register') and resource ('a new Obsidian vault'), including the key arguments (name and path). It distinguishes itself from sibling tools like list_vaults and set_active_vault by implying creation rather than listing or activation.

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 description implies the tool is used when a user wants to add a new vault, but it provides no explicit guidance on when to use it versus alternatives, nor does it mention prerequisites or exclusions. No alternative tools are referenced.

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