Skip to main content
Glama

memory_cleanup

Destructive

Find and remove duplicate memory entries to prevent redundant storage and keep semantic search results accurate.

Instructions

Find and remove duplicate entries

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

C2.7/5.0
Behavior2/5

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

The destructiveHint=true annotation already tells the agent this mutates data, and the description is consistent with that. Beyond consistency, it adds little: it does not say whether deletion is permanent or reversible, which copy in a duplicate set is retained, or whether the whole memory store is scanned. For a zero-parameter, whole-store destructive operation those omissions matter.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, which is good. However, at six words for a destructive, store-wide, parameterless operation it reads as under-specified rather than appropriately sized — concision here comes at the cost of the scope and safety detail an agent needs.

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?

With no parameters, no output schema, and only a destructiveHint annotation, the description is the sole place to convey what gets destroyed and over what scope, and it does neither. An agent cannot tell what a 'duplicate' is by this tool's definition, nor what it will receive back after running it.

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?

The tool takes no parameters, so there is no parameter meaning for the description to supply; the baseline of 4 applies. Nothing in the description misleads about inputs, and the empty schema is self-explanatory.

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

Purpose3/5

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

The description gives a concrete verb pair (find and remove) and an object (duplicate entries), so the agent knows roughly what happens. But 'entries' is never defined (memory records? sessions?), and the scope — whether it scans the entire store or only a session/workspace — is unstated, so it is only partly distinguishable from sibling tools. Adequate but vague at the edges.

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?

There is no statement of when to use this rather than memory_consolidate, memory_conflicts, memory_resolve, or memory_delete, all of which plausibly touch overlapping ground. The agent must infer that cleanup is for de-duplication while consolidation and conflict resolution handle other redundancy cases. No prerequisites or exclusions are mentioned.

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