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

total-agent-memory

by vbcherepanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_exploration_record

Idempotent

Record the conclusion of a codebase exploration together with the SHA-256 of every file read to reach it. Call it after answering a structural question by reading files (how X is wired, where Y is decided).

Instructions

Record the conclusion of a codebase exploration together with the SHA-256 of every file read to reach it. Call it after answering a structural question by reading files (how X is wired, where Y is decided). Paths are stored relative to root (default: the server's working directory); files outside root are refused. Up to 64 files of at most 32 MB each. Recording the same question again for the project replaces the earlier memo.

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": {
      "question": "<question>",
      "conclusion": "<conclusion>",
      "files": "<files>",
      "project": "<project>"
    },
    "name": "memory_exploration_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute project root directory; default: the server's working directory
filesYesFiles read to reach the conclusion: paths relative to root, or absolute paths inside root
projectYesProject name
questionYesThe question the exploration answered, e.g. 'how is auth wired?'
conclusionYesWhat was concluded, self-contained enough to reuse without re-reading

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv14.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description adds real value beyond them by disclosing path-resolution rules (relative to root, outside-root refused), the 64-file/32 MB caps, and the replace-on-repeat semantics that explain the idempotent behavior. Missing only what the stored record returns or how failures surface.

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?

Four sentences, each earning its place: purpose, trigger, path/limit constraints, and replacement semantics. Front-loaded with what the tool does before the caveats.

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?

For a write tool with no output schema and full schema coverage, the description supplies the missing behavioral context: trigger condition, path refusal, size limits, and overwrite semantics. Only the post-write response shape is left implicit, which is minor given the operation's nature.

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 schema already documents root, files, project, question, and conclusion. The description adds only the 32 MB per-file limit (not in schema) and the outside-root refusal rule; the 64-file cap merely restates maxItems. Baseline 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?

States a specific verb and resource — recording an exploration conclusion plus SHA-256 hashes of every file read — which is unmistakably distinct from siblings like memory_exploration_recall or memory_save. The agent knows exactly what artifact this produces.

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 says to call it 'after answering a structural question by reading files (how X is wired, where Y is decided)', which is a clear triggering condition. It does not name the complementary recall tool or state when NOT to use it, so it falls short of the 5 tier.

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