Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by aniketbiswas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_note

Create new notes in an Obsidian vault, including frontmatter properties like tags, aliases, and custom fields.

Instructions

Create a new note in the Obsidian vault. Can include frontmatter properties like tags, aliases, and custom fields.

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

NameRequiredDescriptionDefault
pathYesPath for the new note (e.g., 'folder/note.md'). Will create parent folders if needed.
contentYesThe markdown content for the note.
overwriteNoWhether to overwrite if the note already exists.
frontmatterNoFrontmatter properties to include in the note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose important behavioral traits such as default overwrite behavior, parent folder creation, or conflict handling. The schema provides these details, but the description itself adds minimal behavioral context beyond the basic create action.

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 two concise sentences, front-loaded with the main purpose and followed by a helpful note about frontmatter capabilities. No unnecessary words or repetition.

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

Completeness4/5

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

The schema is rich and covers all parameters with descriptions, and the description provides the tool's core purpose. However, the description lacks any mention of return values or error behavior, and given there is no output schema, this is a minor gap for a create tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explicitly mentioning 'custom fields' in frontmatter, which clarifies that additional frontmatter properties beyond the listed ones are allowed, supplementing the schema's additionalProperties: true.

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 tool creates a new note in the Obsidian vault, which distinguishes it from sibling tools like update_note, append_to_note, and delete_note. It also mentions frontmatter capabilities, further defining its purpose.

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 clearly indicates this is for creating new notes, which implies usage over update/append tools. However, it does not explicitly mention when not to use it or provide alternatives, so it lacks explicit exclusions or alternatives.

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