Skip to main content
Glama

Consolidate / cognify

memory_consolidate

Rebuild a provider’s graph or index after bulk ingest (Cognee cognify) so newly added memory becomes usable; no-op on mem0.

Instructions

Rebuild the provider's graph or index after bulk ingest (Cognee cognify; no-op on mem0).

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
bankNoBank / dataset to consolidate (required for Cognee cognify)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / bank / description
      Added value: +"Bank / dataset to consolidate (required for Cognee cognify)"
  2. First observedv0.6.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds one genuinely useful behavioral fact not in the annotations — that it silently no-ops on mem0 — but says nothing about duration, blocking behavior, or cost, which matter a lot for a full graph rebuild and are the main open question given idempotentHint=false.

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?

A single sentence that front-loads the action and appends the provider caveat. Nothing is padded and every clause carries information.

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 one-parameter tool with full schema coverage and annotations covering the safety profile, the description covers what it does, when to run it, and the provider caveat. The remaining gap — whether the call blocks and what it returns on a no-op or failure — is minor but not entirely negligible for a rebuild operation.

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% and the single `bank` parameter is already documented as "required for Cognee cognify." The description's mention of the provider's graph reinforces that the parameter is provider-scoped, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Rebuild the provider's graph or index") and maps it to the vendor operation (Cognee cognify), which distinguishes it from bulk-ingest siblings like memory_import. It stops short of naming any sibling directly, so an agent must infer the pairing itself.

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?

"after bulk ingest" gives an explicit triggering condition, so the agent knows when to reach for it. There are no stated exclusions or named alternatives, and the "no-op on mem0" note is the only guidance about when it will do nothing useful.

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