Skip to main content
Glama

roam_remember

Save a memory to your Roam daily page, organized with optional categories and headings, and automatically tagged for quick retrieval.

Instructions

Add a memory or piece of information to remember, stored on the daily page with ROAM_MEMORIES_TAG tag and optional categories (unless include_memories_tag is false). NOTE on Roam-flavored markdown: For direct linking: use [[link]] syntax. For aliased linking, use alias syntax. Do not concatenate words in links/hashtags - correct: #[[multiple words]] #self-esteem (for typically hyphenated words). IMPORTANT: Before using this tool, ensure that you have loaded into context the 'Roam Markdown Cheatsheet' resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoryYesThe memory detail or information to remember. Add tags in `categories`.
categoriesNoOptional categories to tag the memory with (will be converted to Roam tags). Do not duplicate tags added in `memory` parameter.
headingNoOptional heading text to nest the memory under (e.g., "Memories" or "## LLM Memories"). If the heading does not exist on the daily page, it will be created. Ignored if parent_uid is provided.
parent_uidNoOptional UID of a specific block to nest the memory under. Takes precedence over heading parameter.
include_memories_tagNoWhether to append the ROAM_MEMORIES_TAG tag to the memory block.
graphNoTarget graph key from ROAM_GRAPHS config. Defaults to ROAM_DEFAULT_GRAPH. Only needed in multi-graph mode.
write_keyNoWrite confirmation key. Required for write operations on non-default graphs when write_key is configured.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses some behaviors (heading creation, parent_uid precedence, default for include_memories_tag) but does not explain idempotency, error handling, or side effects like duplicate memory handling.

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 relatively concise with a front-loaded purpose sentence. The markdown note adds necessary context, though it could be more tightly coupled. Overall efficient.

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?

The description covers main functionality but lacks output/return specification and error handling details. Given no output schema, this is a gap. Adequate for basic use but incomplete for robust tool invocation.

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 coverage is 100%, so the schema fully describes parameters. The description adds marginal value (e.g., markdown note) but does not significantly enhance parameter understanding beyond the schema.

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 the tool's purpose: adding a memory stored on the daily page with a tag. While it implicitly distinguishes from roam_recall (retrieval), it does not explicitly differentiate from other add tools like roam_add_todo.

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 provides a clear context for usage (adding memories) and includes a prerequisite (load Roam Markdown Cheatsheet). However, it lacks guidance on when to avoid using this tool or direct comparisons with alternatives like roam_recall.

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/2b3pro/roam-research-mcp'

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