Skip to main content
Glama

add_memory_entry

Add a human-curated memory entry with title, summary, and topics to a memory palace. Optionally saves detailed markdown notes for future reference.

Instructions

Add a new memory entry to the memory palace.

Use this for a human-curated 'memory palace' note (title + summary + topics,
optionally saved as a markdown file). For machine/agent event logging use
store_episodic_memory; for a distilled concept/definition use
store_semantic_memory.

Inserts into the memory_entries table. If detail is provided, also writes
a markdown file under journal/{entry_type}s/.

Args:
    title: Short title for the entry.
    summary: One-paragraph summary, stored in the DB and shown in search.
    topics: Comma-separated topic tags, e.g. "metis-setup,mcp-server".
    entry_type: One of "session", "journal", "idea", "decision", or "topic".
    detail: Full markdown content for the optional .md file.
    computer: Hostname of the computer this entry is from (optional).

Returns:
    A single TextContent confirming the saved entry (title, generated ID,
    type, topics, and the markdown file path if one was written), or an
    error message if the database is missing or the write fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
summaryYes
topicsYes
entry_typeNojournal
detailNo
computerNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: inserts into memory_entries table, optionally writes a markdown file under journal/{entry_type}s/, and returns a confirmation with details. It also mentions error conditions (missing database or write failure). No contradictions.

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 well-structured, starting with purpose and usage, then behavior, then parameters and return. It is not overly verbose, but the parameter descriptions could be slightly more concise without losing clarity. Still, it earns a high score for efficient information delivery.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, optional markdown writing, multiple entry types) and lack of output schema, the description fully covers behavior, parameter semantics, return values, and error scenarios. It is complete for an agent to use correctly.

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

Parameters5/5

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

The schema has 0% description coverage, but the description's 'Args' section adds meaningful explanations for each parameter: e.g., 'Comma-separated topic tags' for topics, 'One of ...' for entry_type, 'Full markdown content' for detail. This greatly enhances understanding beyond the raw schema.

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 clearly states that the tool adds a memory entry to a 'memory palace' for human-curated notes, distinguishing it from machine event logging (store_episodic_memory) and concept storage (store_semantic_memory). The verb 'Add' and resource 'memory entry' are specific and unambiguous.

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?

Explicitly provides when-to-use and when-not-to-use: 'Use this for a human-curated memory palace note... For machine/agent event logging use store_episodic_memory; for a distilled concept/definition use store_semantic_memory.' This clearly differentiates from sibling tools.

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/SVerITG/Metis'

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