Skip to main content
Glama
sureshsankaran

Obsidian Tools MCP Server

append_to_note

Add content to the end of an existing note in your Obsidian vault. Specify the note path and content to append, with optional separator formatting.

Instructions

Append content to the end of an existing note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the note relative to vault root
contentYesContent to append
separatorNoSeparator to add before appended content. Default: '\n\n'

Implementation Reference

  • The handler function that reads an existing note, appends the provided content with an optional separator, and writes it back to the file.
    async function handleAppendToNote(args: {
      path: string;
      content: string;
      separator?: string;
    }): Promise<string> {
      const fullPath = resolvePath(args.path);
      const separator = args.separator ?? "\n\n";
    
      if (!(await fileExists(fullPath))) {
        throw new Error(`Note not found at ${args.path}`);
      }
    
      const existingContent = await fs.readFile(fullPath, "utf-8");
      const newContent = existingContent + separator + args.content;
      await fs.writeFile(fullPath, newContent, "utf-8");
      return `Successfully appended content to ${args.path}`;
    }
  • The input schema definition for the append_to_note tool, including parameters for path, content, and optional separator.
    {
      name: "append_to_note",
      description: "Append content to the end of an existing note",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description: "Path to the note relative to vault root",
          },
          content: {
            type: "string",
            description: "Content to append",
          },
          separator: {
            type: "string",
            description:
              "Separator to add before appended content. Default: '\\n\\n'",
            default: "\n\n",
          },
        },
        required: ["path", "content"],
      },
  • src/index.ts:878-882 (registration)
    The switch case in the main tool call handler that dispatches to the append_to_note handler function.
    case "append_to_note":
      result = await handleAppendToNote(
        args as { path: string; content: string; separator?: string }
      );
      break;
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 core action but lacks critical details: whether this operation is idempotent, what happens if the note doesn't exist, if there are permission requirements, rate limits, or how conflicts are handled. For a mutation tool with zero annotation coverage, this leaves significant behavioral unknowns.

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 states the core functionality without unnecessary words. It's front-loaded with the main action and resource, making it easy to parse. Every word earns its place, with no redundancy or fluff.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover error conditions, success responses, or behavioral nuances like whether the append is atomic or if there are side effects. Given the complexity of file system operations and the lack of structured safety hints, more context is needed for reliable agent use.

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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what the schema provides—it doesn't clarify path format (e.g., relative to vault root, file extensions), content constraints, or separator usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Append content') and target resource ('to the end of an existing note'), making the purpose immediately understandable. It distinguishes from sibling tools like 'prepend_to_note' by specifying 'to the end', but doesn't explicitly differentiate from other note modification tools like 'update_note' or 'insert_at_heading' beyond the append action.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the note must exist), when to choose this over 'update_note' or 'insert_at_heading', or any constraints like file size limits. The agent must infer usage from the tool name and sibling list 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/sureshsankaran/obsidian-tools-mcp'

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