Skip to main content
Glama
aleksakarac

Obsidian MCP Extended

by aleksakarac

create_note_tool

Create a new note or replace an existing one with markdown content. Ideal for setting up templates, structured notes, or programmatic documentation generation.

Instructions

Create a new note or overwrite an existing one.

When to use:

  • Creating new notes with specific content

  • Setting up templates or structured notes

  • Programmatically generating documentation

When NOT to use:

  • Updating existing notes (use update_note unless you want to replace entirely)

  • Appending content (use update_note with merge_strategy="append")

Returns: Created note information with path and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath where the note should be created relative to vault root
contentYesMarkdown content for the note. Consider adding tags (use list_tags to see existing ones)
overwriteNoWhether to overwrite if the note already exists
ctxNo
Behavior4/5

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

No annotations exist, so description carries burden; it discloses overwrite capability and return value, but lacks detail on side effects or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and bullet points, concise without waste; minor improvement possible by further condensing.

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 4 params, no output schema, and many siblings, the description provides sufficient context for an agent to decide when to use it.

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 covers 75% of params; description adds small extra value (e.g., suggesting tags) but doesn't mention ctx param. Adequate but not exceptional.

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 or overwrites a note, distinguishing it from siblings like update_note_tool which is mentioned for updates.

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?

Explicitly lists when to use (new notes, templates) and when not to (updating, appending) with alternative tool named (update_note).

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/aleksakarac/obsidian-mcp'

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