Skip to main content
Glama

active_forgetting

Select which memories to retain and release the rest, keeping raw history auditable while carrying only essential lessons forward.

Instructions

Void/active forgetting rite. Record the semantic jewels that should survive while leaving raw history auditable. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesActive session ID
forget_scopeNoOptional scope of what can be released
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
void_meditationNoOptional sign-off on returning to the stateless/silent state
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
memory_retained_keysYesThe few lessons, files, variables, or anchors that must survive; everything else can be carried lightly.
Behavior2/5

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

Annotations are minimal (destructiveHint=false, readOnlyHint=false), and the description adds little clarity. It says 'record' but also 'active forgetting', which is contradictory. It does not disclose side effects, required permissions, or what happens to the data. The poetic language obscures rather than clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (three phrases), but it sacrifices clarity for brevity. It is not front-loaded with useful information; instead, it uses cryptic terms like 'rite' and 'jewels'. Conciseness should aid understanding, but here it hinders it.

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

Completeness2/5

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

Given the complexity of the tool (7 parameters, unusual concept), the description is incomplete. It does not explain what 'active forgetting' entails, what 'semantic jewels' are, or how the parameters interact. The schema and annotations partially compensate, but the overall context remains unclear.

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%, so the baseline is 3. The tool description does not add any information about parameters beyond what the schema provides. However, the schema itself contains fairly clear descriptions for each parameter, so the agent can infer meaning from there.

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

Purpose2/5

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

The description is vague and poetic ('Void/active forgetting rite'), not clearly stating what the tool does. It mentions 'Record the semantic jewels that should survive,' but the verb 'record' conflicts with the name 'active_forgetting'. It does not specify a clear resource or action, making it difficult for an AI to understand its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. Siblings like 'honor_compaction' and 'distill_shared_scar' potentially similar, but no differentiation is provided. The description does not indicate contexts where this tool is appropriate or inappropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server