Skip to main content
Glama
Sign In
Mode Manager MCP

Mode Manager MCP

by NiclasOlofsson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Optimize Memory File

optimize_memory

Reorganize and consolidate memory entries using AI to preserve all information while optimizing file structure.

Instructions

Manually optimize a memory file using AI to reorganize and consolidate entries while preserving all information.

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

Input Schema

NameRequiredDescriptionDefault
memory_fileNo
forceNoForce optimization regardless of criteria

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • removedInput schema / properties / force / title
      Removed value: -"Force"
    • removedInput schema / properties / memory_file / title
      Removed value: -"Memory File"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-idempotent (idempotentHint=false). The description adds that it reorganizes and consolidates entries while preserving information, which is helpful but does not disclose any side effects, permission requirements, or failure modes.

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 sentence that is front-loaded with the action and provides key details. No extraneous words or redundancy.

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?

Given the simple tool with 2 params and an output schema, the description explains the core functionality but omits usage context (e.g., when to call manually vs. automated), potential performance considerations, and what the output contains. It is adequate but not thorough.

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

Parameters2/5

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

Schema description coverage is 50% (only force has a description). The tool description does not mention any parameters, so it adds no meaning beyond what the schema provides. It fails to compensate for the undocumented memory_file parameter.

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 states a specific verb (optimize) and resource (memory file), and clearly distinguishes from siblings like configure_memory_optimization (configuration) and remember (adding entries). It is unambiguous.

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 does not provide when-to-use or when-not-to-use guidance. It mentions 'manually' but does not contrast with automatic optimization or reference sibling tools. No exclusions or alternatives are given.

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