obsidian-mcp

obsidian_list_vaults

Read-onlyIdempotent

List configured Obsidian vaults and identify the current default vault, helping you verify available vaults before making API calls. Reads configuration only, so it works safely without contacting Obsidian.

Instructions

List every configured vault, showing which one unqualified calls will hit.

Reads configuration only — it does not contact Obsidian, so it is cheap and safe to call first when you are unsure which vaults exist. For live reachability, use obsidian_backend_status.

Returns: str: JSON of the shape {"current_vault": str, "count": int, "vaults": [{"name": str, "description": str|null, "path": str|null, "rest_base_url": str|null, "backends": ["rest"|"filesystem"], "is_current": bool, "is_default": bool}]} On failure: "Error: "

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

While annotations already declare readOnlyHint, idempotentHint, and destructiveHint, the description adds meaningful behavior beyond those: it reads configuration only retaining does not contact Obsidian, and it documents the failure string shape. This gives the agent an accurate model of side effects and cost.

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 core purpose is front-loaded, followed by concise usage guidance and a structured return block. Every sentence earns its place, and the return format block is dense but directly useful rather than filler.

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 zero parameters, comprehensive safety annotations, a clear usage recommendation, a named sibling alternative, and a documented return shape, nothing essential is missing. An agent can reliably decide when to call this tool and correctly interpret its result.

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?

The tool has zero parameters)Skip, so schema coverage is trivially 100%. The description has no parameter details to provide, which is expected and acceptable; the baseline score of 4 applies given the parameter-less signature.

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 and resource: 'list every configured vault' and clarifies the key value of showing which vault unqualified calls will target. This clearly distinguishes it from sibling tools like obsidian_backend_status and vault-mutating tools.

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?

It explicitly states when to call the tool ('call first when you are unsure which vaults exist') and why it is appropriate ('cheap and safe'). It also names the alternative for a different need — obsidian_backend_status for live reachability — providing a clear when-to-use vs. when-not-to-use boundary.

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

Deploy Server