Skip to main content
Glama
moorcheh-ai
by moorcheh-ai

remember

Store user facts, preferences, and decisions in long-term memory with confidence and provenance for reliable recall in future conversations.

Instructions

Store a single piece of information in the agent's long-term memory. Use this whenever the user shares a stable fact, preference, decision, goal, or instruction you should recall in a future conversation. Memory is typed (13 categories) and carries confidence + provenance so later retrievals can rank and filter intelligently. Content is capped at 10000 chars - store atomic, self-contained statements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional lowercase tag list for later filtering.
typeNoSemantic memory type. Use 'preference' for likes/styles, 'fact' for stable factual claims, 'decision' for choices the user has made, 'goal' for objectives, 'instruction' for explicit how-to directives, 'event' for things that happened, 'observation' for inferred behavior.fact
titleNoShort label (<= 100 chars). If omitted, derived from content.
sourceNoFree-form label for the source of this memory (e.g. 'user', 'web', 'tool-call', or your agent name).mcp-agent
contentYesThe memory itself - one atomic statement. Max 10000 characters.
agent_idNoMemanto agent identifier the memory belongs to (required: no MEMANTO_DEFAULT_AGENT_ID is configured).
confidenceNoHow sure you are this is true (0.0-1.0). Use 1.0 only for things the user stated explicitly. 0.6-0.8 is a sensible default for inferred information.
provenanceNoHow this memory was obtained. 'explicit_statement' means the user said it; 'inferred' means you deduced it; 'observed' means you saw it during a tool call; 'corrected' means it overrides an earlier wrong memory.explicit_statement

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes'ok' on success, 'error' otherwise.
messageNoHuman-readable detail.
agent_idYesAgent the memory belongs to.
memory_idNoMemanto-assigned ID.
namespaceNoUnderlying namespace.
confidenceNoConfidence stored.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses memory typing, confidence, provenance, character limit, and atomic storage requirement. Sufficiently transparent for a memory write operation.

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?

Three concise sentences, front-loaded with main purpose, no fluff. 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?

Comprehensive given complexity: 8 parameters fully described in schema, output schema exists (so no need to explain returns). Description covers usage, constraints, and behavioral notes adequately.

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?

Schema description coverage is 100%, baseline score is 3. Description adds no significant parameter-specific details beyond what schema already provides (e.g., type enum meanings, confidence range).

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?

Clearly states verb 'store' and resource 'information in long-term memory'. Differentiates from siblings like batch_remember (single vs batch) and recall tools (store vs retrieve).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this whenever the user shares a stable fact, preference, decision, goal, or instruction'. Provides context but does not list when not to use, though inference is clear.

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/moorcheh-ai/memanto'

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