Skip to main content
Glama
sureshsankaran

Obsidian Tools MCP Server

create_note

Create new notes in Obsidian vaults with Markdown content, supporting nested folders and optional overwrite functionality.

Instructions

Create a new note in the Obsidian vault. Supports nested folder creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath for the new note relative to vault root (e.g., 'folder/note.md')
contentYesContent of the note in Markdown format
overwriteNoIf true, overwrite existing note. Default: false

Implementation Reference

  • The handler function that executes the create_note tool: resolves the full path, checks for existence and overwrite flag, ensures directory exists, writes the file content, and returns success message.
    async function handleCreateNote(args: {
      path: string;
      content: string;
      overwrite?: boolean;
    }): Promise<string> {
      const fullPath = resolvePath(args.path);
    
      if (!args.overwrite && (await fileExists(fullPath))) {
        throw new Error(
          `Note already exists at ${args.path}. Use overwrite: true to replace.`
        );
      }
    
      await ensureDir(fullPath);
      await fs.writeFile(fullPath, args.content, "utf-8");
      return `Successfully created note at ${args.path}`;
    }
  • Input schema defining parameters for create_note: path (string, required), content (string, required), overwrite (boolean, optional default false).
    inputSchema: {
      type: "object",
      properties: {
        path: {
          type: "string",
          description:
            "Path for the new note relative to vault root (e.g., 'folder/note.md')",
        },
        content: {
          type: "string",
          description: "Content of the note in Markdown format",
        },
        overwrite: {
          type: "boolean",
          description: "If true, overwrite existing note. Default: false",
          default: false,
        },
      },
      required: ["path", "content"],
    },
  • src/index.ts:25-49 (registration)
    Tool registration in the tools array, including name, description, and input schema, used for ListTools response.
    {
      name: "create_note",
      description:
        "Create a new note in the Obsidian vault. Supports nested folder creation.",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description:
              "Path for the new note relative to vault root (e.g., 'folder/note.md')",
          },
          content: {
            type: "string",
            description: "Content of the note in Markdown format",
          },
          overwrite: {
            type: "boolean",
            description: "If true, overwrite existing note. Default: false",
            default: false,
          },
        },
        required: ["path", "content"],
      },
    },
  • src/index.ts:865-869 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes 'create_note' calls to the handleCreateNote function.
    case "create_note":
      result = await handleCreateNote(
        args as { path: string; content: string; overwrite?: boolean }
      );
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Supports nested folder creation', which adds useful behavioral context beyond the basic creation action. However, it does not disclose critical traits like whether this requires specific permissions, how errors are handled (e.g., if path is invalid), or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 sentences with zero waste: the first sentence states the core purpose, and the second adds a key feature. It is front-loaded with the main action and efficiently conveys essential information without redundancy or fluff.

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?

Given the tool has no annotations and no output schema, the description is moderately complete. It covers the basic purpose and a notable feature (nested folder creation), but lacks details on behavioral aspects like error handling or return values. For a creation tool with 3 parameters and rich sibling context, it should provide more guidance on usage and outcomes to be fully helpful.

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 schema fully documents all three parameters (path, content, overwrite). The description does not add any parameter-specific details beyond what the schema provides, such as examples for nested folders or Markdown formatting tips. With high schema coverage, the baseline is 3, as the description does not compensate but also does not detract.

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 verb 'Create' and the resource 'new note in the Obsidian vault', specifying the action and target. It distinguishes from siblings like 'append_to_note' or 'update_note' by emphasizing creation of a new note, and adds unique value with 'Supports nested folder creation', which is not obvious from the name alone.

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 new notes, but does not explicitly state when to use this tool versus alternatives like 'create_from_template' or 'update_note'. It mentions nested folder creation as a feature, which provides some context, but lacks clear guidance on prerequisites, exclusions, or specific scenarios where this is the preferred choice.

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

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