Skip to main content
Glama

memory_write

Idempotent

Store a self-contained fact with provenance and bitemporal tracking. Use to capture user-stated preferences, decisions, or project details for reliable recall across sessions.

Instructions

Store a durable, provenanced fact (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?

Description adds significant behavioral context beyond annotations: dedup, bitemporal, 403 for shared writes by non-admins, writing guidelines (wayback test). No contradiction with annotations.

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?

Description is thorough but slightly verbose; however, every sentence earns its place. Front-loaded main purpose then details. Could be trimmed slightly but effective.

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?

Covers all aspects: provenance, space restrictions, writing guidelines, dedup/bitemporal. With full schema coverage and output schema present, the description adds complete context for correct invocation.

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?

Schema coverage is 100%, but description adds meaning to value (self-contained, word count, no pronouns) and space (routing, permissions). Provides usage semantics beyond 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?

Description clearly states it stores a durable, provenanced fact with dedup and bitemporal properties. It distinguishes from siblings like memory_recall by specifying when to call: whenever the user states a fact, preference, decision, or project detail.

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 says when to use: whenever user states a fact or asks to remember. Provides when-not-to-use: shared space writes only for team owners/admins, and guidance on writing style (self-contained, absolute dates).

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