Skip to main content
Glama

write_note

Write Markdown notes to chosen paths in an Obsidian vault, creating shared long-term memory for MCP clients while protecting existing notes unless overwrite is set.

Instructions

Write a note at any path. Paths outside Claude/ are rejected unless confirm_outside_claude=true, and that flag is only for writes the user asked for in so many words. An existing note is kept unless overwrite=true.

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": "write_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
contentYes
overwriteNo
confirm_outside_claudeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key write behavior: paths outside Claude/ are rejected, the confirm flag is narrowly scoped, and existing notes are preserved unless overwrite=true. It leaves out secondary behavior such as parent-directory creation or permission requirements, but since an output schema exists, return values need not be explained here.

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 three sentences, front-loaded with the core action and immediately followed by the two operational constraints. Every sentence contributes necessary meaning, and there is no redundant restatement of the tool name.

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?

For a four-parameter mutation tool with no annotations, the description covers the critical safety and overwrite semantics. It does not address directory creation, encoding, or failure modes beyond the outside-path rejection, but the output schema covers return values and the remaining gaps are minor.

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 0%, so the description must supply parameter meaning. It explains path scope and the outside-Claude rejection rule, the confirm_outside_claude gating condition, and the overwrite default; content is only implied by "Write a note." The important non-obvious parameters are covered well.

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 first sentence states a specific verb and resource: "Write a note at any path." It clearly positions the tool as the write operation, distinct from read_note and query/search tools. An agent can identify what this tool does without opening the schema.

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 gives conditional policy for confirm_outside_claude and overwrite, which implies when those options should be used. However, it does not explicitly compare this tool to siblings such as capture or upsert_concept, so the overall when-to-use guidance remains implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.