Skip to main content
Glama

append_to_note

Add content to existing notes in Obsidian vaults. Append text to files while maintaining formatting with optional newline control.

Instructions

Append content to the end of an existing note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path to the note
contentYesContent to append
ensureNewlineNoEnsure content starts on a new line (default: true)

Implementation Reference

  • The appendToNote function, which implements the logic for appending content to a file.
    export async function appendToNote(
      vaultPath: string,
      relativePath: string,
      content: string,
    ): Promise<void> {
      const fullPath = resolveVaultPath(vaultPath, relativePath);
      const existing = await fs.readFile(fullPath, "utf-8");
      const separator = existing.endsWith("\n") ? "" : "\n";
      await fs.writeFile(fullPath, existing + separator + content, "utf-8");
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'append' implies a write operation, it doesn't specify permissions needed, whether the operation is idempotent, error conditions (e.g., if note doesn't exist), or what happens with concurrent modifications. The description mentions the action but lacks crucial behavioral context for safe invocation.

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 appropriately sized for a straightforward tool and gets directly to the point with zero wasted text.

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 insufficient. It doesn't explain what happens on success (e.g., returns updated content, confirmation message), error conditions, or important behavioral aspects like whether the operation creates the note if it doesn't exist. Given the complexity of file system operations and lack of structured safety information, more context is needed.

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 doesn't add any meaningful parameter semantics beyond what's already in the schema - it mentions 'content' and implies 'path' through 'existing note' but provides no additional context about format, constraints, or usage patterns. This meets the baseline for high schema coverage.

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 ('to the end of an existing note'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'prepend_to_note' (which adds content to the beginning) or 'update_frontmatter' (which modifies metadata rather than content), leaving some ambiguity about when to choose this specific tool.

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 sibling tools like 'prepend_to_note' for adding content to the beginning, 'create_note' for new notes, or 'update_frontmatter' for metadata changes. There's also no information about prerequisites (e.g., note must exist) or typical use cases.

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

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