Skip to main content
Glama
ManuelWarland

MemCore

by ManuelWarland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Entry history

memory_history
Read-onlyIdempotent

Show prior versions of an entry overwritten or deleted, newest first, to recover or compare earlier content. Read-only.

Instructions

Show the prior versions of one entry that were overwritten or deleted, newest first.

Every write that replaces an entry keeps the previous version automatically, so nothing is silently lost even if another agent overwrote it. Use it to recover or compare earlier content. For who made each change use memory_events; for the current version, memory_get. Read-only, available even on a read-only connection. Returns an empty list when the entry has no prior versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEntry name: the short kebab-case slug that identifies the entry within its scope.
limitNoMaximum number of versions to return (default 20). Values are clamped to 1-200.
scopeYesProject/topic scope the entry belongs to, e.g. a project folder name (list them with memory_scopes). On a scope-locked connection (--scope), this argument is ignored and the connection's own scope is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of versions to return (default 20). Values are clamped to 1-200."
    • addedInput schema / properties / name / description
      Added value: +"Entry name: the short kebab-case slug that identifies the entry within its scope."
    • addedInput schema / properties / scope / description
      Added value: +"Project/topic scope the entry belongs to, e.g. a project folder name (list them with memory_scopes). On a scope-locked connection (--scope), this argument is ignored and the connection's own scope is used."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/idempotentHint annotations by disclosing the automatic version-retention model, that an empty list is returned when there is no history, and that the tool works even on a read-only connection. These are non-obvious traits an agent needs.

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?

Front-loads the core action and keeps the routing hints in a compact clause. The sentence about write behavior is slightly explanatory overhead, but it earns its place as rationale for trusting the history.

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?

With an output schema present, the description needn't explain return shape, yet it still notes the empty-list case. Combined with sibling routing and read-only availability, nothing an agent needs to call this correctly is missing.

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 coverage is 100% and all three parameters are already documented in the schema, including clamping for limit and scope-locked connection behavior. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Show the prior versions of one entry that were overwritten or deleted, newest first'), including the ordering. An agent can distinguish it from memory_get and memory_events without opening a schema.

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 names both alternatives and the condition that selects them: memory_events for authorship, memory_get for the current version. It also names the triggering task ('recover or compare earlier content').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools