Skip to main content
Glama
Sign In
Enhanced Knowledge Graph Memory Server

Enhanced Knowledge Graph Memory Server

by danielsimonjr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

clear_expired_memories

Remove expired working memories from the knowledge graph to prevent stale data accumulation.

Instructions

Remove all working memories that have exceeded their TTL. Complements get_expired_entities (which lists but does not delete).

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": "clear_expired_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv12.7.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It states 'remove' indicating a destructive action but omits details on permissions, irreversibility, or side effects. This lack of depth is concerning for a deletion operation.

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 two sentences with no filler. It efficiently communicates the action and relationship to a sibling tool, making it clear and easy to parse.

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 simple deletion tool with no parameters or output schema, the description provides minimal but essential context. However, it lacks information about scope (e.g., current session or all), potential outcomes (e.g., success message), and safety considerations, leaving some ambiguity.

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 input schema has zero parameters, so the description naturally does not need to add parameter information. The baseline for zero parameters is 4, and the description is adequate in this regard.

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 action ('Remove all working memories that have exceeded their TTL') and distinguishes from the sibling tool 'get_expired_entities' by contrasting listing vs deletion.

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 implies use for deletion while referencing a complementary tool for listing, providing clear context. However, it does not explicitly state when not to use or alternative tools beyond the mentioned sibling.

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