Skip to main content
Glama
quinny1187

Obsidian MCP Server

by quinny1187

list_vaults

Discover and access available Obsidian vaults for file system operations, enabling direct interaction with notes through auto-discovery without plugins or REST API.

Instructions

List available Obsidian vaults

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that discovers available vaults using VaultManager and returns a list with paths, names, last modified dates, and total count.
    export async function handleListVaults(vaultManager: VaultManager) {
      const vaults = await vaultManager.discoverVaults();
      
      return {
        vaults: vaults.map(v => ({
          path: v.path,
          name: v.name,
          lastModified: v.lastModified,
        })),
        count: vaults.length,
      };
    }
  • Tool definition including name, description, and empty input schema for list_vaults.
    {
      name: 'list_vaults',
      description: 'List available Obsidian vaults',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:172-174 (registration)
    Switch case in the tool call handler that dispatches to the list_vaults handler function.
    case 'list_vaults':
      result = await handleListVaults(vaultManager);
      break;
  • src/index.ts:16-16 (registration)
    Import statement that brings in the handleListVaults function from the tools module.
    import { handleGetVaultInfo, handleListVaults } from './tools/vault.js';
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 the tool lists vaults but doesn't describe return format (e.g., list of names, paths, metadata), pagination, error conditions, or any side effects. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence ('List available Obsidian vaults') directly contributes to understanding the tool's function, making it optimally concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimal but adequate for basic understanding. However, with no annotations and no output schema, it lacks details on behavioral aspects like return format or error handling. For a list operation, this leaves gaps in contextual completeness.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't add parameter details beyond this, which is appropriate. Baseline 4 is correct for zero-parameter tools, as there's no need to compensate for schema gaps.

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?

The description clearly states the action ('List') and resource ('available Obsidian vaults'), making the purpose immediately understandable. It distinguishes from siblings like 'get_vault_info' (detailed info) and 'search_vault' (search within vaults), though it doesn't explicitly mention this differentiation. The description avoids tautology by not just restating the tool name.

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 explicit guidance is provided on when to use this tool versus alternatives like 'get_vault_info' or 'search_vault'. The description implies usage for listing vaults but doesn't specify scenarios, prerequisites, or exclusions. This leaves the agent to infer context from sibling tool names alone.

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/quinny1187/obsidian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server