Skip to main content
Glama

Advanced: store XMemo memory

store_memory

Store a memory with full control over fields like path, type, importance, and expiration. Use for advanced memory operations requiring explicit field-level specification.

Instructions

Low-level memory write with full field control. Use only when a caller needs explicit field-level control; for normal conversational capture use remember.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesA simple user-facing category or path for this memory, such as preferences, projects/xmemo, or personal/travel.
scopeNoOptional scope that narrows memory access; leave blank for the token default.
bucketNoMemory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.public
contentYesText body to save, such as a memory, TODO/action item, event note, or state summary.
team_idNoOptional team/workspace identifier for team-scoped memory access.
agent_idNoOptional client-supplied agent label for memory attribution.
device_idNoOptional client-supplied device identifier for attribution.
confidenceNoConfidence score for the saved or updated memory, from 0.0 to 1.0.
expires_atNoOptional ISO 8601 expiration timestamp for the memory.
importanceNoImportance score for the saved or updated memory, from 0.0 to 1.0.
memory_typeNoMemory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.semantic
device_labelNoOptional human-readable device label for attribution.
semantic_keyNoOptional stable semantic key used to identify or upsert a memory concept.
metadata_jsonNoOptional JSON object string with extra metadata for the operation.{}
embedding_jsonNoOptional JSON array or object containing a precomputed embedding; leave blank for normal use.
provenance_jsonNoOptional JSON object string describing memory source, evidence, or attribution.{}
agent_instance_idNoOptional stable, non-secret agent instance ID for per-client attribution.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate it's not read-only or destructive. The description adds 'low-level memory write' implying full field control but doesn't elaborate on side effects, auth needs, or limits. Adequate but not enriched beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and usage guidance. No filler, every sentence adds value.

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

Completeness4/5

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

Given the large number of parameters (17) and output schema presence, the description combined with schema provides sufficient context. It lacks details on return structure or error cases, but output schema likely covers that.

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?

With 100% schema coverage, the baseline is 3. The description does not add additional meaning beyond what the schema provides for each parameter, just notes 'full field control' generically.

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 the tool does memory writing with full field control, and contrasts it with 'remember' for normal capture, making the purpose 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 tells when to use this tool ('explicit field-level control') and when not to ('for normal conversational capture use remember'), providing a clear alternative.

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/yonro/memory-os-cli'

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