Skip to main content
Glama

obsidian_save_note

Writes a markdown note into an Obsidian vault, creating new files by default or appending and overwriting when specified, with automatic backups and read-only protection unless the human enables AI edits.

Instructions

Write a markdown note into the vault. REFUSED unless the human enabled writes ("Let AI edit my notes" in UnClick's Obsidian vault settings, or OBSIDIAN_VAULT_WRITABLE=1; the vault is read-only for AI by default). When allowed: create by default, append/overwrite explicit, the previous version is always backed up first, and writes never leave the vault or enter folders marked .ai-private.

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": {
      "note": "<note>",
      "content": "<content>"
    },
    "name": "obsidian_save_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoDefault create (refuses to clobber)
noteYesVault-relative path, e.g. 'Inbox/From UnClick.md'
contentYes
vault_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: discloses the refusal condition, the permission toggle, that create is the default and won't clobber, that append/overwrite must be explicit, that backups always occur first, and that writes stay in the vault and skip .ai-private. This is rich behavioral context beyond the schema.

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?

Front-loaded with the core action, followed by the gate, then the write semantics. Every clause earns its place with no 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?

No output schema and no annotations, so the description must cover behavior for a mutation tool — it does thoroughly, with the only real omission being vault_path semantics. Nearly complete.

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 note (path example) and mode (enum + 'Default create (refuses to clobber)'), so 50% coverage. The description reinforces mode semantics (create/append/overwrite explicit) but says nothing about vault_path, one of the two undocumented params, leaving a gap.

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 (write) and resource (a markdown note into the vault), and is immediately distinguishable from the read/list/search siblings.

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?

Gives a strong precondition for use (human must enable writes via settings or OBSIDIAN_VAULT_WRITABLE=1, read-only by default) and clarifies mode selection. It doesn't explicitly route to obsidian_read_note or obsidian_vault_status, but the write context is unambiguous.

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