Skip to main content
Glama

memory_ingest

Persist important context and information to memory for future recall. Store project decisions, user preferences, and any data worth remembering.

Instructions

Save important context to persistent memory — be proactive. Call this WHENEVER you learn information that would be valuable in a future conversation: project decisions ('we chose Postgres because X'), architectural choices, user preferences, debugging insights, recurring patterns, deadlines, stakeholder context, or any 'remember this' / 'save this' / 'note that' style request from the user. Heuristic: if you would be sad to lose this fact when the conversation ends, ingest it. Better to over-save than to under-save — the memory_query semantic search will surface what's relevant later. Always pass meaningful title and tags so the item is discoverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for categorization
titleNoOptional title for the content
contentYesThe content to store in memory
categoryNoOptional category
space_idNoSpace UUID (uses default if not specified)
source_uriNoOptional source URI (file path, URL, etc.)
source_typeNoType of source (default: manual)
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) with no destructive effects (destructiveHint=false). The description adds context about persistence and retrieval via memory_query, but does not cover potential limitations like size or rate limits. It adds value beyond annotations without contradiction.

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 a single, well-structured paragraph that front-loads the core purpose. It is moderately long but clear and efficient, with no wasted sentences.

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 no output schema and a straightforward input schema, the description covers the tool's purpose, usage context, and parameter hints thoroughly. It references sibling tools and provides enough information for an agent to decide and invoke correctly.

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 advises passing meaningful title and tags for discoverability, but does not add deep semantic meaning beyond the schema. Slight value added.

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 saves important context to persistent memory, with examples and a proactive heuristic. It distinguishes from sibling tools like memory_query and memory_delete by specifying that this tool is for saving data.

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 provides extensive guidance on when to use the tool: whenever learning valuable information, with concrete examples and a heuristic ('sad to lose'). It implicitly suggests alternatives like memory_query for retrieval, giving clear context.

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/alfredoizdev/contextforge-mcp'

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