Skip to main content
Glama

Consolidate Namespace Memories

consolidate
Idempotent

Deduplicates memories in a namespace, links superseded records, and promotes recurring high-salience episodic memories to the Semantic tier.

Instructions

Deduplicate memories within a namespace, link superseded records, and promote recurring high-salience episodic memories to Semantic tier.

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": {
      "namespace": "<namespace>"
    },
    "name": "consolidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceYesNamespace to consolidate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about deduplication, linking superseded records, and tier promotion, but does not explain reversibility, permission requirements, or what happens to linked records.

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 a single front-loaded sentence with no wasted wording. It efficiently lists the three main operations performed by the tool.

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?

For a mutation tool with no output schema, the description covers the main operations but leaves out important behavioral details such as what deduplication does to conflicting records, how superseded links are represented, and what the caller receives. Annotations cover safety hints, but the description could do more to complete the picture.

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% for the single namespace parameter, and the description only restates that consolidation happens within a namespace. It adds no syntax, format, or scoping details beyond the schema.

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 uses specific verbs and resources: deduplicate memories, link superseded records, and promote episodic memories to Semantic tier. It clearly states the tool's purpose, though it does not explicitly differentiate itself from siblings such as forget_memory or encode_memory.

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?

The description explains what consolidation does but gives no explicit guidance on when to use it versus alternatives like forget_memory, encode_memory, or recall_memories. Usage is only implied by the maintenance-oriented wording.

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