Skip to main content
Glama

bardo_note_update

Update note content and metadata: replace, append, or find-and-replace text; change title, summary, tags, pinned status, or lock state. Conflicts are detected on concurrent edits.

Instructions

Edit a note. Give at most one text-edit mode:

  • text: replace the whole thing

  • append_text: add to the end

  • find + replace: find must match the current text exactly once Editing text creates a new version (old wording stays in history); title/summary/tags/pinned update in place with no history kept. Give none of the text modes to change only metadata. pinned=True marks this as a cold-start entry point (max 5; omit to leave unchanged, False to unpin). clear (e.g. ["title"]) sets a field back to unset rather than leaving it unchanged. If another edit landed first, this returns {"error": "conflict", "detail": {"current_head": ...}} — re-read before retrying.

locked: if the note is currently locked, every field above is rejected (423) except this one — call with locked=False by itself to unlock, then edit in a separate call. Set locked=True (alone, or alongside a final edit) to freeze it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findNo
tagsNo
textNo
clearNo
titleNo
lockedNo
pinnedNo
note_idYes
replaceNo
summaryNo
append_textNo
session_tokenNo
Behavior5/5

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

Discloses behavioral traits beyond annotations: text edits create a new version with history, metadata updates are in-place, conflict error structure, locked note handling, and pin limit. No contradiction with annotations.

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?

Description is detailed and well-structured with bulleted modes, but could be slightly more concise. Every sentence adds value, though length is justified by complexity.

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?

Complex tool with many parameters and edge cases; description covers conflict and lock behavior but lacks specification of success response (no output schema). Missing output description slightly reduces completeness.

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?

With 0% schema coverage, description adds meaning to most parameters (text modes, clear, pinned, locked, title, summary, tags). However, session_token and note_id lack explanation, and inter-relationships are well covered but not exhaustive.

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?

Description clearly states 'Edit a note' and lists specific editing modes (text, append_text, find+replace) and metadata fields, distinguishing it from related tools like bardo_note_add.

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?

Provides explicit guidance: 'Give at most one text-edit mode', explains when to use metadata-only, conflict handling, and locked note behavior. Alternative actions clearly stated.

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/calebe/bardo'

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