Skip to main content
Glama
Sign In
DecisionsSearch

DecisionsSearch

by Renzo-Tognella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory.consolidate

Consolidate memory immediately or deferred, with scope options to manage which data is persisted.

Instructions

Dispara consolidação imediata ou diferida.

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.consolidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodeferred
scopeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are present, so the description carries full behavioral transparency burden. It mentions immediate or deferred but fails to disclose what consolidation entails (e.g., idempotency, blocking behavior, side effects on other memories). The description is insufficient for an agent to predict tool behavior.

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 description is a single sentence with no wasted words, but it is under-specified. Conciseness should not sacrifice completeness; here it is too brief to be effective. A 3 reflects acceptable brevity with inadequate content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, two undocumented parameters, and a large set of sibling tools, the description fails to provide sufficient context. An agent cannot determine what consolidation does, what to expect as output, or how to set parameters correctly. The description is far too incomplete.

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 coverage is 0%, so the description must explain parameters. The mention of 'immediate or deferred' partially clarifies the mode parameter, but the scope parameter is entirely unexplained. The description adds marginal value beyond raw schema but does not fully compensate for the coverage gap.

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 states it triggers consolidation and mentions immediate or deferred modes, giving a clear verb and resource. However, it does not specify what consolidation means in this context or differentiate it from sibling tools like memory.reconcile or memory.reflect, making its purpose somewhat vague.

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

Usage Guidelines1/5

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

No usage guidance is provided. The description does not indicate when to use consolidation vs other memory operations, when to choose immediate vs deferred, or any prerequisites or consequences. This is a critical omission.

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