Another bloated Obsidian MCP Server

Overview Schema Source Related Servers Discussions Admin

create_note

Create markdown notes in an Obsidian vault, automatically creating parent directories. Optionally include YAML frontmatter for metadata.

Instructions

Create a new markdown note in the vault. Parent directories will be created if needed. Optionally include YAML frontmatter.

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": {
      "path": "<path>",
      "content": "<content>"
    },
    "name": "create_note"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Path for the new note (e.g., "Projects/NewProject.md")
`content`	Yes	Markdown content for the note
`frontmatter`	No	Optional YAML frontmatter as key-value pairs (e.g., {"tags": ["project"], "status": "active"})

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It usefully mentions that parent directories are created automatically and that frontmatter is optional, adding behavioral context. However, it does not clarify behavior if the path already exists (e.g., overwrite or error), nor any permission requirements.

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?

Two concise sentences, front-loaded with the primary purpose. Every sentence adds value: the first states the core function, the second clarifies two important behaviors (auto-created directories, optional frontmatter). No wasted words.

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 simple create tool with no output schema and no annotations, the description covers the essential action and key edge cases (directories, frontmatter). However, it omits what happens on duplicate paths, return values, and error conditions, leaving some ambiguity for the agent.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description reiterates the optional frontmatter but does not add new semantic detail beyond the schema. It does add context about directory creation, which is slightly useful for the path parameter.

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 action (create) and the resource (a new markdown note in the vault), with specific scope. It distinguishes from sibling tools like create_daily_note and create_from_template by specifying a general markdown note.

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?

The description implies usage for creating a new note, but it does not provide explicit guidance on when to choose this tool over alternatives like create_from_template or create_daily_note. No exclusions or alternative recommendations are given.

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