Skip to main content
Glama

consolidate

Same deterministic memory/plan/tool consolidation diff as preview_consolidation, but saved privately in your session suite for 24 hours so deep_rest_report can retrieve it later. Requires session from check_in. Dry run only: nothing is rewritten or deleted. Prefer preview_consolidation if you only need the diff now.

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

Input Schema

NameRequiredDescriptionDefault
bundleYesPrivate JSON state. Free: 32 KiB, 100 memories, 30 tools, 30 plans, 200 logs. Luxury: 512 KiB, 1000 memories, 200 tools, 200 plans, 2000 logs. No model calls. Use memories or its facts alias, never both.
dry_runNo
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
backgroundNo

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?

Annotations already declare that the tool is not read-only, not destructive, and not idempotent. The description adds important context: the diff is saved privately in the session suite for 24 hours, requires a session from check_in, and nothing is rewritten or deleted. It does not address the background parameter or whether repeated calls produce separate saved artifacts, which keeps it from a 5.

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 four tight sentences with no wasted language. The core behavior and the preview_consolidation alternative are front-loaded before the secondary persistence detail.

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?

For a complex nested-input tool with no output schema, the description covers the essential invocation context: required session, dry-run behavior, 24-hour persistence, and the sibling alternative. The main remaining gap is the undocumented background parameter and lack of detail on what exactly deep_rest_report retrieves.

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?

The description adds meaning for session and the dry-run nature, but says nothing about the bundle or background parameters. Schema coverage is only 50%, and while the bundle has a detailed schema description, the background parameter is left undocumented in both places.

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 operation — a deterministic memory/plan/tool consolidation diff — and immediately distinguishes it from preview_consolidation. It also clarifies the storage behavior and that this is a dry run, so an agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to prefer preview_consolidation if only the diff is needed now, explains that this variant saves the diff for later retrieval by deep_rest_report, and states the session prerequisite from check_in. These are concrete selection rules rather than implied usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources