Skip to main content
Glama
bezata

kObsidian MCP

Create Note Or Folder

notes.create

Create notes and folders in an Obsidian vault. Specify note path and content; choose error, replace, or skip if exists. Folders are idempotent. Works with active vault or explicit path.

Instructions

Create a new note or folder in the vault. kind:'note' creates a markdown note at path with the given content; ifExists controls collision behavior (error = fail, default; replace = overwrite; skip = no-op). kind:'folder' creates a directory at path (intermediate folders are created automatically; idempotent — re-creating an existing folder is a no-op). Returns the standard mutation envelope.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Create a new note, failing if it exists:

{
  "kind": "note",
  "path": "Journal/2026-04-24.md",
  "content": "# Today\n"
}

Example 2 — Ensure a folder exists (idempotent):

{
  "kind": "folder",
  "path": "Projects/Alpha/Reports"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
targetYesThe path or identifier the tool acted on.
summaryYesShort human-readable summary of what happened.
Behavior2/5

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

The description details creation behavior, collision handling, and idempotent folder creation, but contradicts the annotation idempotentHint=false by claiming folder creation is idempotent. This contradiction undermines trust. Annotations are all false, leaving the description as the sole source for behavioral traits.

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 well-structured, front-loaded with the core purpose, followed by detailed parameter explanations and concrete JSON examples. Every sentence adds value without redundancy.

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?

Given the tool's complexity (two modes, collision, idempotency, vault scoping) and that an output schema exists, the description covers most aspects. However, the lack of parameter definitions in the input schema is a significant gap that the description partially addresses but cannot fully resolve.

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?

The input schema is empty, yet the description introduces parameters (kind, path, content, ifExists, vaultPath). While the description adds essential meaning beyond the schema, the mismatch is confusing. Schema coverage is 100% only because there are no schema parameters.

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 note or folder, with distinct behaviors for each kind. It distinguishes this tool from siblings like notes.edit and notes.delete by focusing on creation.

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 guidance on when to use note vs folder, details collision handling (ifExists), and explains vault scoping. However, it does not explicitly contrast with other tools for updates or deletions, missing clear alternatives.

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/bezata/kObsidian'

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