Skip to main content
Glama
isiomaC

memstack

by isiomaC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

memory_dry_run_prune

Preview which memories would be pruned by a strategy without deleting them. Returns the IDs of memories that match the criteria.

Instructions

Preview what would be pruned by a given strategy WITHOUT actually deleting. Scoped to a single actor — defaults to the current session actor. Returns the memory IDs that would be removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPrune strategy type to preview. Note: 'custom' is not available via MCP because it requires a JS function.
maxAgeNoMax age in seconds (for byAge)
actorIdNoActor ID to scope pruning to. Defaults to the current session actor.
maxPerActorNoMaximum memories per actor (for byCount)
memoryTypesNoMemory types to evaluate (for byType)
minImportanceNoMinimum importance (for byImportance)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description explicitly states that no deletion occurs, which is the primary side-effect concern. It also mentions the return value (memory IDs). Since annotations are absent, this is the sole source of transparency, and it covers the key behavioral aspect.

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?

The description is concise, consisting of two sentences that efficiently convey the purpose, scope, and output. No unnecessary information or repetition is present.

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?

The description provides sufficient context for a preview tool: it states the output (memory IDs) and the scope (single actor, default). While it does not detail what the agent should do with the returned IDs, that is implied by the preview nature. The lack of an output schema is mitigated by the clear mention of the output type.

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

Parameters4/5

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

All 6 parameters are described with brief but sufficient explanations. The note about 'custom' not being available via MCP adds useful context. The descriptions are clear enough for an agent to understand what each parameter does.

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?

The description clearly states the tool's purpose: previewing what would be pruned without actually deleting. It specifies the scope (single actor, defaulting to current session) and the output (memory IDs).

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?

The description implicitly distinguishes this from the actual prune tool by emphasizing 'WITHOUT actually deleting,' which guides the agent to use this when a dry-run is needed. However, it does not explicitly name the alternative or provide a direct when-to-use statement.

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

This server cannot be deployed

Other Tools