Skip to main content
Glama
LogicLabsAI

UltraMemory

Official
by LogicLabsAI

Memory Write

memory_write
Idempotent

Save a durable fact about a person, project, or thing with self-contained text and provenance. Use to remember user preferences, decisions, or project details for any AI.

Instructions

Store a durable fact the user will want remembered — provenanced, deduped, bitemporal. Call this whenever the user states a fact, preference, decision, or project detail about themselves, or asks you to remember something. source tags provenance. space: 'private' (default — your own space) or 'shared' (the team space). Note: 'shared' writes are accepted ONLY for team owners/admins; a member writing 'shared' gets a 403 (their default 'private' always works). Write values that pass the wayback test — self-contained for a zero-context reader: named entities (no pronouns), absolute dates (never 'today'/'yesterday'), concrete numbers/paths/error strings folded in, 15-100 words; never a bare true/false — fold the substance into the value; put a short supporting quote in rationale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesAttribute name for the fact (e.g. 'status', 'preference')
scopeNoProject scope id (default 'default')default
spaceNoMemory space routing: 'private' (default — your own space) or 'shared' (the team space)private
valueYesThe fact text itself — self-contained for a zero-context reader
entityYesSubject the fact is about (a named person, project, or thing)
sourceNoProvenance tag for where the fact came frommcp
rationaleNoShort supporting quote or why this was saved

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dedupedNoTrue if an identical fact already existed (no new row written)
fact_idNoId of the stored (or deduped) fact — usable with fetch
supersededNoHow many prior facts this write superseded
Behavior5/5

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

The description adds behavioral details beyond annotations: 'shared writes are accepted ONLY for team owners/admins; a member writing shared gets a 403.' It also mentions deduped and bitemporal properties, which align with idempotentHint=true.

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 moderately long but well-structured, front-loading the purpose and then providing usage rules. Every sentence adds value, though it could be slightly tighter.

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 7 parameters, 100% schema coverage, full annotations, and the presence of an output schema (though not detailed), the description is complete. It covers behavioral quirks, parameter semantics, and usage context.

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?

Despite 100% schema coverage, the description adds significant value for parameters, especially `value`: 'self-contained for a zero-context reader: named entities (no pronouns), absolute dates..., 15-100 words; never a bare true/false.' This enriches the schema's bare descriptions.

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 specifies 'Store a durable fact' with clear verb and resource, and distinguishes from siblings like memory_recall and playbook_write. It explicitly says what the tool does and its scope.

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?

It directly states when to use: 'Call this whenever the user states a fact, preference, decision, or project detail about themselves, or asks you to remember something.' This provides clear guidance and implies alternatives.

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/LogicLabsAI/ultramemory-mcp'

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