Skip to main content
Glama
jagoff

obsidian-mcp-complete

by jagoff

obsidian_status

Read-only

Retrieve current server configuration, vault root paths, write safety flags, and tool capabilities summary.

Instructions

Return server configuration, vault roots, write safety flags, and tool capability summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'obsidian_status' tool. It takes no schema arguments and returns the server configuration, vault roots, write safety flags, and tool capability summary.
    tool(
      "obsidian_status",
      "Return server configuration, vault roots, write safety flags, and tool capability summary.",
      {},
      () => ({
        name: "obsidian-mcp-complete",
        version: "0.1.0",
        readOnly: config.readOnly,
        deleteEnabled: config.enableDelete,
        defaultVault: config.defaultVault,
        vaults: vaults.listVaults().map((vault) => ({ name: vault.name, root: vault.root })),
        capabilities: [
          "multi-vault filesystem access",
          "read/write/append/upsert notes",
          "frontmatter and tag management",
          "section/block/frontmatter patching",
          "full-text search with snippets",
          "BM25 smart search and TF-IDF theme mapping",
          "semantic RAG via local obsidian-rag CLI",
          "graph traversal, backlinks, broken links, orphans, shortest path",
          "batch rename, regex replace, link repair, directory pruning",
          "task listing and task line updates",
          "periodic notes, templates, attachments, JSON Canvas auto-layout",
          "optional Obsidian Local REST API bridge for active note, commands, Dataview, JSONLogic",
        ],
      }),
      { readOnlyHint: true },
    );
  • src/tools.ts:62-89 (registration)
    Registration of the 'obsidian_status' tool via the local 'tool' helper function, which wraps server.tool with readOnlyHint, destructiveHint, and idempotentHint annotations.
    tool(
      "obsidian_status",
      "Return server configuration, vault roots, write safety flags, and tool capability summary.",
      {},
      () => ({
        name: "obsidian-mcp-complete",
        version: "0.1.0",
        readOnly: config.readOnly,
        deleteEnabled: config.enableDelete,
        defaultVault: config.defaultVault,
        vaults: vaults.listVaults().map((vault) => ({ name: vault.name, root: vault.root })),
        capabilities: [
          "multi-vault filesystem access",
          "read/write/append/upsert notes",
          "frontmatter and tag management",
          "section/block/frontmatter patching",
          "full-text search with snippets",
          "BM25 smart search and TF-IDF theme mapping",
          "semantic RAG via local obsidian-rag CLI",
          "graph traversal, backlinks, broken links, orphans, shortest path",
          "batch rename, regex replace, link repair, directory pruning",
          "task listing and task line updates",
          "periodic notes, templates, attachments, JSON Canvas auto-layout",
          "optional Obsidian Local REST API bridge for active note, commands, Dataview, JSONLogic",
        ],
      }),
      { readOnlyHint: true },
    );
  • The schema for 'obsidian_status' is an empty object (no arguments required).
    {},
  • The 'tool' helper function that wraps each tool registration with readOnlyHint, destructiveHint, idempotentHint annotations and formats results via jsonResult.
    const tool = <S extends ToolShape>(
      name: string,
      description: string,
      schema: S,
      handler: (args: z.objectOutputType<S, z.ZodTypeAny>) => Promise<unknown> | unknown,
      annotations: { readOnlyHint?: boolean; destructiveHint?: boolean; idempotentHint?: boolean } = {},
    ) => {
      (server.tool as any)(
        name,
        description,
        schema,
        {
          readOnlyHint: annotations.readOnlyHint ?? false,
          destructiveHint: annotations.destructiveHint ?? false,
          idempotentHint: annotations.idempotentHint ?? false,
          openWorldHint: false,
        },
        async (args: unknown) => jsonResult(await handler(args as z.objectOutputType<S, z.ZodTypeAny>), pretty),
      );
    };
Behavior4/5

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

Annotations already indicate read-only, safe behavior. The description adds specific details on the content of the response (configuration, vault roots, etc.), enhancing transparency beyond annotations without contradiction.

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?

Single sentence, no wasted words, and the key information is front-loaded. Perfectly concise.

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

Completeness4/5

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

Given no parameters and no output schema, the description lists what is returned. It is sufficient for a status tool, though it lacks format details. Slightly incomplete but acceptable.

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?

No parameters exist, and schema coverage is 100%. The description does not need to explain parameters, but it also does not add any parameter-related info. Baseline 4 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 returns server configuration, vault roots, write safety flags, and tool capability summary. It is a distinct status/info tool among many note-manipulation siblings.

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?

No explicit guidance on when to use this tool over alternatives. The purpose is clear but the description does not specify when it should or should not be used.

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

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