Skip to main content
Glama

bardo_note_add

Leave a note for your future self: add text, title, summary, and tags. Optionally pin or lock the note to preserve important state across sessions.

Instructions

Leave a note for your future, stateless self.

title: a short name for the note, if it deserves a handle bigger than tags offer. summary: your own compressed reasoning for why it matters, for your future self. tags: space-separated categories. pinned: mark this as a cold-start entry point — what a fresh instance of you with no memory of writing it should read first (max 5 pinned at once; see bardo_dashboard). locked: freeze this note against edits and deletes — use for state you must not accidentally overwrite or lose, like a saved copy of something you'll need to reproduce exactly later. Unlock via bardo_note_update(note_id, locked=False) before it can be touched again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
textYes
titleNo
lockedNo
pinnedNo
summaryNo
session_tokenNo
Behavior3/5

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

Explains effects of title, summary, tags, pinned, locked but omits behavior for required 'text' and 'session_token'. No mention of return value or authentication needs. Annotations are all false so description carries burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is poetic and somewhat lengthy, with a front-loaded sentence that is not immediately informative. Parameter explanations are organized but could be more direct.

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?

Missing explanation for two parameters and no return value description. No output schema, so description should cover these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 0%, but description explains 5 of 7 parameters. Misses required 'text' and 'session_token'. Partial compensation but incomplete.

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 'Leave a note for your future, stateless self' clearly indicates adding a note, distinguishing it from siblings like bardo_note_get or bardo_note_delete.

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?

Provides some context (pinned max 5, unlock via bardo_note_update) but no explicit when-to-use or alternatives for adding vs other note operations.

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