Skip to main content
Glama
rps321321

obsidian-mcp-pro

by rps321321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Note

create_note

Creates a new Markdown note at a specified path with body content and optional YAML frontmatter. It refuses to overwrite existing notes, auto-creates missing folders, and appends .md when omitted.

Instructions

Create a new markdown note at the given path with body content and optional YAML frontmatter. Fails (does not overwrite) if a note already exists at that path — use append_to_note, prepend_to_note, or update_frontmatter for existing notes. Missing directories are created automatically, and a .md extension is appended if omitted.

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path from vault root, e.g., 'folder/note.md' or 'note' (.md added automatically)
contentYesMarkdown body content for the note (rendered below the frontmatter block if any)
frontmatterNoJSON object string of frontmatter key-value pairs (e.g., '{"status":"draft","tags":["idea"]}'). Rendered as YAML at the top of the note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.0.0
  3. Removedv1.9.0
  4. Addedv0.1.6
  5. Removedv0.1.4
  6. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / content / description
      Previous value: -"Note content"New value: +"Markdown body content for the note (rendered below the frontmatter block if any)"
    • changedInput schema / properties / frontmatter / description
      Previous value: -"JSON string of key-value pairs to add as YAML frontmatter"New value: +"JSON object string of frontmatter key-value pairs (e.g., '{\"status\":\"draft\",\"tags\":[\"idea\"]}'). Rendered as YAML at the top of the note."
    • changedInput schema / properties / path / description
      Previous value: -"Relative path like 'folder/note.md'"New value: +"Relative path from vault root, e.g., 'folder/note.md' or 'note' (.md added automatically)"
  7. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds valuable context beyond annotations: it fails rather than overwrites on conflict, creates missing directories automatically, and appends .md if omitted. This clarifies failure behavior and side effects, though it doesn't mention permissions or return values.

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?

Three sentences, front-loaded with the core action, then failure behavior and alternatives, then automatic side effects. No wasted words, each sentence adds specific value.

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

Completeness5/5

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

Given the complexity of a create operation with 3 parameters at 100% schema coverage and no output schema, the description covers usage, failure modes, and automatic behaviors completely. Nothing essential for correct invocation is missing.

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 input schema already documents all three parameters (path, content, frontmatter) with examples and constraints. The description adds no additional parameter-level semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb (Create) and resource (markdown note at given path) with body and optional frontmatter. Explicitly distinguishes from sibling tools for existing notes (append_to_note, prepend_to_note, update_frontmatter).

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

Usage Guidelines5/5

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

Clearly states when to use this tool (creating new notes) and when not to (existing notes), naming alternative tools for those cases. Provides explicit prerequisites like automatic directory creation and .md extension handling.

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

Deploy Server

Other Tools