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

total-agent-memory

by vbcherepanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_save_fast

Save memory records instantly by bypassing the quality gate and LLM processing. Use for fast, direct storage when you need low-latency persistence without additional analysis.

Instructions

v11.0: same as memory_save but routes through the fast hot path (skip_quality=True, no LLM, no async-blocking). Use when you want to bypass the v10 quality gate without flipping the env flag.

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": {
      "content": "<content>",
      "type": "<type>"
    },
    "name": "memory_save_fast"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
typeYes
branchNo
filterNo
contentYes
contextNo
projectNogeneral
agent_idNoOptional Claude Code subagent ID (v2.1.139+)
supersedeNoSame as memory_save.supersede: retire records this one gives a new value for.
importanceNomedium
source_formatNoauto
parent_agent_idNoOptional parent agent ID (the dispatching span)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv14.5.0
    • addedInput schema / properties / supersede
      Added value: +{
+  "default": false,
+  "description": "Same as memory_save.supersede: retire records this one gives a new value for.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv14.0.0
    • addedInput schema / properties / source_format
      Added value: +{
+  "default": "auto",
+  "enum": [
+    "auto",
+    "conversation"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description adds behavioral details like 'skip_quality=True, no LLM, no async-blocking' beyond the annotations, which is valuable. However, it doesn't describe return values, side effects, or permissions, and the annotations (readOnlyHint=false, etc.) indicate a write operation without full transparency on what the write entails.

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?

A single, efficient sentence that front-loads the purpose and then gives the usage condition. No wasted words; it is both concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 parameters, no output schema), the description is only partially complete. It covers the key differentiator from memory_save and provides usage guidance, but lacks details on behavior, return values, and parameter semantics, making it insufficient for an agent unfamiliar with memory_save.

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

Parameters2/5

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

The schema has 12 parameters but only 25% have descriptions, and the tool description provides no additional parameter explanations. It merely refers to memory_save without elaborating on any of the parameters, leaving the agent to infer from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly indicates this tool saves memory, and the 'fast hot path' clarifies it is a variant of memory_save. It distinguishes itself from siblings by explicitly referencing memory_save, though it doesn't fully describe the saving behavior on its own.

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?

It explicitly states when to use this tool: 'when you want to bypass the v10 quality gate without flipping the env flag.' It also names the alternative (memory_save) implicitly, providing clear routing guidance.

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