Skip to main content
Glama
memstate-ai

Memstate AI - Agent Memory System

Official

memstate_history

View version history for stored data to debug past states, audit changes, or recover previous values in the Memstate AI memory system.

Instructions

View version history for a keypath or memory chain. Use when you need to see how a value changed over time.

USE THIS WHEN: Debugging past state, auditing changes, or recovering a previous value. NOT FOR: Reading current content (use memstate_get) or saving (use memstate_remember or memstate_set).

memstate_history(project_id="myapp", keypath="config.database.port") memstate_history(memory_id="mem_abc123")

Returns all versions with timestamps; latest is marked is_latest=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoRequired with keypath
keypathNoGet history for this keypath
memory_idNoOr get history for a specific memory chain by ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool 'memstate_history' is dynamically proxied by this handler, which 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 the full burden of behavioral disclosure. It effectively describes the tool's behavior: it returns 'all versions with timestamps' and marks the latest with 'is_latest=true.' However, it lacks details on potential limitations like rate limits, pagination, or error conditions, which would be helpful for a read operation with historical data.

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 well-structured and front-loaded: it starts with the core purpose, followed by usage guidelines, examples, and return details. Every sentence adds value—no waste. The use of bold headers and code examples improves readability without unnecessary verbosity.

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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is complete enough. It covers purpose, usage, parameters, and return values. Since an output schema exists, the description doesn't need to explain return values in detail, and it adequately addresses the context provided by sibling tools and schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by clarifying parameter semantics: it explains that 'project_id' is 'Required with keypath' (though this is also in the schema) and provides example usage with both 'keypath' and 'memory_id', showing how they are used alternatively. This enhances understanding beyond the schema's basic descriptions.

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: 'View version history for a keypath or memory chain.' It specifies the verb ('view') and resource ('version history'), and distinguishes it from siblings by explicitly naming alternatives (memstate_get for current content, memstate_remember/memstate_set for saving). This is specific and avoids tautology.

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 usage guidelines with dedicated sections: 'USE THIS WHEN:' lists debugging, auditing, and recovery scenarios, and 'NOT FOR:' explicitly names when not to use it (reading current content or saving) and specifies alternative tools (memstate_get, memstate_remember, memstate_set). This gives clear context and exclusions.

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