Skip to main content
Glama
memstate-ai

Memstate AI - Agent Memory System

Official

memstate_remember

Save markdown, text, or task summaries to automatically create structured memories with keypath extraction, organization, and versioning for AI agents.

Instructions

Save markdown, task summaries, or any text. Server extracts keypaths and creates structured memories automatically. This is the PREFERRED way to save information.

USE THIS WHEN: Saving task summaries, meeting notes, docs, or any text with multiple facts. The server handles organization, conflict detection, and versioning. NOT FOR: Setting one specific keypath to a short value (e.g. config.port = "8080") — use memstate_set for that.

memstate_remember(project_id="myapp", content="## Task Summary\n- Added OAuth\n- Files: auth.go, middleware.go", source="agent") memstate_remember(project_id="myapp", content="Architecture decision: migrated to JWT tokens for session management")

Content limit: 100,000 chars. Processing is async (~15-18s); returns job_id immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesRequired. Project to store in (e.g. 'myapp'). Auto-creates if new.
contentYesMarkdown or text to remember (max 100,000 chars). Server extracts keypaths and creates structured memories automatically.
sourceNoSource type: agent, readme, docs, meeting, code
contextNoOptional hint to guide keypath extraction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The memstate_remember tool is dynamically proxied by the MCP server, so its execution is handled by a generic tool call handler that forwards the request to the remote Memstate MCP server.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      return await remote.callTool({
        name: request.params.name,
        arguments: request.params.arguments,
      });
    });
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: content limit (100,000 chars), async processing with timing (~15-18s), immediate job_id return, automatic project creation, and server-side organization/conflict detection/versioning. It doesn't mention error conditions or retry behavior, keeping it from a perfect score.

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?

The description is efficiently structured with clear sections, front-loaded key information, and every sentence adds value. It uses bold headings for guidance, includes practical examples, and provides critical constraints without unnecessary elaboration.

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 the tool's complexity (async processing, automatic extraction), 100% schema coverage, and presence of an output schema, the description provides excellent context. It covers purpose, usage guidelines, behavioral traits, constraints, and examples, making it complete enough for an agent to understand when and how to use this tool effectively.

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%, so the baseline is 3. The description adds minimal parameter semantics beyond the schema: it reinforces content limits and provides example values in the code snippets, but doesn't significantly enhance understanding of parameters beyond what the schema already documents well.

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's purpose: 'Save markdown, task summaries, or any text' with server-side extraction of keypaths and structured memory creation. It explicitly distinguishes from sibling tools by stating this is the 'PREFERRED way to save information' and contrasting with memstate_set for specific keypath assignments.

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 explicit guidance with dedicated 'USE THIS WHEN:' and 'NOT FOR:' sections, listing specific use cases (task summaries, meeting notes, docs) and clear exclusions (setting one specific keypath to short values). It names the alternative tool (memstate_set) for excluded scenarios.

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/memstate-ai/memstate-mcp'

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