Skip to main content
Glama
HenriqueCSouzza

Obsidian MCP Local

append_to_note

Append text content to an existing Markdown note in your Obsidian vault. Specify the note path and content to add, enabling efficient note augmentation without opening Obsidian.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
contentYes

Implementation Reference

  • Registers the 'append_to_note' tool on the MCP server with a Zod schema for 'path' (string, min 1) and 'content' (string, min 1) inputs. The handler calls appendToNote() from vault and returns the result as JSON.
    export function register(server: McpServer): void {
      server.registerTool(
        "append_to_note",
        {
          inputSchema: {
            path: z.string().min(1),
            content: z.string().min(1),
          },
        },
        async ({ path, content }) => {
          const result = await appendToNote(path, content);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          };
        },
      );
    }
  • Input schema definition for the 'append_to_note' tool: 'path' (string, min 1) and 'content' (string, min 1), using Zod validation.
    server.registerTool(
      "append_to_note",
      {
        inputSchema: {
          path: z.string().min(1),
          content: z.string().min(1),
        },
  • Handler function that receives validated 'path' and 'content', calls the vault-level appendToNote() function, and returns the result serialized as JSON text.
    async ({ path, content }) => {
      const result = await appendToNote(path, content);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    },
  • Core appendToNote implementation: resolves the path with .md extension, checks existence, appends content (with leading newline if needed) using fs.appendFile, and returns {path, appended: true}.
    export async function appendToNote(relativePath: string, content: string) {
      const finalPath = ensureMdExtension(relativePath);
      const fullPath = resolveVaultPath(finalPath);
    
      if (!(await pathExists(fullPath))) {
        throw new Error(`Note not found: ${finalPath}`);
      }
    
      const prefix = content.startsWith("\n") ? "" : "\n";
      await fs.appendFile(fullPath, `${prefix}${content}`, "utf-8");
    
      return {
        path: finalPath,
        appended: true,
      };
    }
  • src/server.ts:5-5 (registration)
    Imports the append-to-note tool module in the server.
    import * as appendToNote from "./tools/append-to-note.js";
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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