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

total-agent-memory

by vbcherepanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_observe

Record lightweight observations to track file changes, tool usage, and session activity, with automatic cleanup after 30 days.

Instructions

Save a lightweight observation (auto-capture). No dedup, no ChromaDB — fast and cheap. Use for tracking file changes, tool usage, and session activity. Observations auto-cleanup after 30 days.

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": {
      "tool_name": "<tool_name>",
      "summary": "<summary>"
    },
    "name": "memory_observe"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNogeneral
summaryYesWhat happened (e.g. 'Modified auth controller')
tool_nameYesWhich tool triggered this (Write, Edit, Bash, etc.)
files_affectedNoList of affected file paths
observation_typeNoType of observationchange

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Discloses key behaviors beyond annotations: auto-capture, no dedup, no ChromaDB, fast/cheap, and 30-day auto-cleanup, which informs the agent about retention and performance characteristics.

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?

Two sentences, no fluff, main action and differentiators front-loaded.

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?

Sufficiently complete for a simple save tool; includes purpose, retention, and performance; no output schema needed, though could mention return value or side effects.

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 already covers most parameter descriptions (80%); description adds no extra parameter-level detail, so 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?

Clearly states it saves lightweight observations for tracking file changes, tool usage, and session activity, and differentiates from heavier memory tools by noting absence of dedup and ChromaDB.

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?

Explicitly identifies use cases (tracking file changes, tool usage, session activity) and implies alternative for lightweight, fast, cheap saves with 30-day auto-cleanup; could be more explicit about contrasting with memory_save but enough.

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