Skip to main content
Glama
Sign In
agent-memory-os

agent-memory-os

by yamantaka520
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_snapshot_diff

Compare a session's two most recent snapshots to identify added, removed, and changed keys. Get a summary of changes since the last time work was parked.

Instructions

Show what changed between a session's two most recent context snapshots.

    Answers "what did I change since I last parked this work?" — returns the
    top-level keys added, removed, and changed between the previous and latest
    snapshot, or an `{"error": ...}` object if the session has fewer than two.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "memory_snapshot_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession id whose two most recent snapshots should be compared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / session_id / description
      Added value: +"Session id whose two most recent snapshots should be compared."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It clearly states the tool returns a diff or an error object, implying read-only behavior. It does not mention authentication or side effects, but for a read-only tool the description is sufficient.

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?

Description is concise: one-line summary followed by a short paragraph with additional context. Every sentence adds value. Front-loaded with the primary purpose.

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?

Given no output schema, the description adequately explains return value (top-level keys added/removed/changed). It covers purpose, usage scenario, and error condition. Could mention that snapshots are per session, but is inferred.

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% with clear parameter description. The tool description adds contextual usage (the 'parked work' question) but no additional semantic detail beyond the schema. Baseline score of 3 is appropriate.

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?

Description uses specific verb 'Show' and specifies resource 'what changed between a session's two most recent context snapshots'. It clearly distinguishes from sibling tools (e.g., memory_search, memory_update) by focusing on introspection of snapshot diffs. Return structure (added/removed/changed keys) is explicitly stated.

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?

Description provides a user-facing question ('What did I change since I last parked this work?') indicating when to use. It also mentions error condition (fewer than two snapshots). However, it does not explicitly list alternatives or cases where this tool should not be used.

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