Skip to main content
Glama

Metis ยท Memory Curator โ€” Add Memory Entry

add_memory_entry

Add a human-curated memory entry with title, summary, and topic tags to your memory palace, with optional detailed markdown content.

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
detailNo
topicsYes
summaryYes
computerNo
entry_typeNojournal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It explains that the tool inserts into a database table and optionally writes a markdown file, and describes the return value. It lacks details on permissions or side effects, but is generally transparent.

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 with sections (purpose, usage, args, returns) and is front-loaded. It is slightly long but every sentence is informative, earning its place.

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, 3 required) and the presence of an output schema, the description fully covers input semantics, behavior (database insert and optional file write), and return format. No gaps remain.

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?

With 0% schema description coverage, the description adds comprehensive meaning for each parameter, including allowed values for 'entry_type', comma-separated format for 'topics', and the role of 'detail' in creating a markdown file. This goes well beyond the basic 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 'Add a new memory entry to the memory palace' with a specific verb and resource, and explicitly distinguishes itself from sibling tools 'store_episodic_memory' and 'store_semantic_memory'.

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?

The description explicitly guides when to use this tool ('human-curated memory palace note') and when to use alternatives ('For machine/agent event logging use store_episodic_memory; for a distilled concept/definition use store_semantic_memory').

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