Obsidian MCP Server

append_to_daily_note

Add content to today's daily note, creating the note if needed. Specify a section header and folder for organized daily tracking.

Instructions

Append content to today's daily note. Creates the daily note if it doesn't exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "append_to_daily_note"
  }
}

Input Schema

Name	Required	Description
`content`	Yes	Content to append to daily note
`section`	No	Section header to append under (e.g., '## Claude Sessions')
`daily_folder`	No	Folder for daily notes (default: 'Daily Notes')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 20, 2026

TDQS

A3.9/5.0

Behavior3/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 effectively describes the core behavior (appending with conditional creation) but lacks details about permissions, file format, error handling, or whether appending adds newlines. It's adequate but has clear gaps for a mutation tool without annotations.

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 extremely concise with just two sentences that are front-loaded and waste no words. Every phrase ('Append content to today's daily note', 'Creates the daily note if it doesn't exist') directly contributes to understanding the tool's purpose and behavior.

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

Completeness3/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 covers the basic operation adequately but lacks important contextual details. It doesn't explain what the tool returns (e.g., success confirmation, note content), error conditions, or how it interacts with the note-taking system's conventions, leaving gaps in completeness.

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 the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, such as examples for 'section' beyond what the schema provides. This meets the baseline of 3 when schema coverage is high.

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 specific action ('Append content') and resource ('today's daily note'), including the conditional creation behavior. It distinguishes from sibling tools like 'append_to_note' by specifying 'daily note' and 'today's', and from 'write_note' by focusing on appending rather than overwriting.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: for appending to today's daily note, with automatic creation if missing. However, it doesn't explicitly state when not to use it or name alternatives like 'append_to_note' for non-daily notes or 'write_note' for overwriting, which would be needed for a score of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server