Skip to main content
Glama

manage-notes

List, read, write, move, delete, rename, duplicate, and append notes in an Obsidian vault. Perform actions with pagination, optimistic concurrency, and link updates.

Instructions

Unified tool for listing, reading, writing, moving, deleting, renaming, and appending to notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'read', 'write', 'delete', 'append', 'rename', 'duplicate', 'move', 'list'
pathNoPath to the note relative to vault root
contentNoContent of the note
expected_mtimeNoExpected file modification time (RFC3339Nano) for optimistic concurrency
dry_runNoPreview deletion without modifying files
positionNoPosition to insert: 'end' (default), 'start', 'before', 'after'
afterNoHeading or text to insert after (if position is 'after')
beforeNoHeading or text to insert before (if position is 'before')
context_linesNoNumber of context lines to return (default 0)
old_pathNoOld note path
new_pathNoNew note path
outputNoOutput note path
sourceNoSource path
destinationNoDestination path
update_linksNoWhether to update links to this file (default true)
directoryNoDirectory path relative to vault root (for list action)
limitNoMaximum number of notes to return (for list action, 0 = no limit)
offsetNoNumber of notes to skip for pagination (for list action, default 0)
modeNoResponse mode: compact (default) or detailed
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It does not disclose side effects (e.g., overwriting on write, irreversibility of delete), concurrency handling, or required permissions. The agent learns nothing about the tool's impact beyond the action names.

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?

The description is a single sentence that front-loads the key purpose (unified tool) and lists actions concisely. No wasted words, though it could be broken into bullet points for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (19 parameters, multiple actions), the description is minimal. It lacks information about return values, error cases, parameter-action mappings, and output format. No output schema exists, so more description is needed.

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 each parameter is already documented in the input schema. The description adds no extra meaning beyond listing the actions. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that it is a unified tool for listing, reading, writing, moving, deleting, renaming, and appending to notes, giving a specific verb+resource combination. However, it does not differentiate from sibling tools like 'edit-note' or 'manage-folders', which may overlap in functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'edit-note' for more specific editing). It only lists actions without context or exclusions, leaving the agent to infer usage.

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/zach-snell/obx'

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