Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_consolidate

Destructive

Run a manual memory consolidation pass to merge stored sources into compacted knowledge. Use dry_run to preview proposed operations before any changes are written.

Instructions

Run a manual knowledge consolidation pass. Set dry_run=true to preview the proposed operations without applying them. A pass that reaches the LLM can run for minutes and may outlast your client's own tool-call timeout; the server finishes it either way and holds a run lock while it does, so a retry returns 409 rather than starting again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoPreview operations without writing changes. Recommended when invoking from MCP — the tool is annotated destructive.
nightlyNoRun the nightly compaction prompt instead of the default write-time pass.
sourcesNoMemory directories to consolidate, e.g. `["insights"]`. Defaults to `daily` only.
respect_gateNoApply the activity gate the automatic cron path uses (enough time elapsed AND enough sessions since the last pass); reports `deferred` instead of running when a pass is not yet due.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.1
    • addedInput schema / properties / respect_gate
      Added value: +{
+  "default": false,
+  "description": "Apply the activity gate the automatic cron path uses (enough time elapsed AND enough sessions since the last pass); reports `deferred` instead of running when a pass is not yet due.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.10.1
    • addedInput schema / properties / sources
      Added value: +{
+  "description": "Memory directories to consolidate, e.g. `[\"insights\"]`.  Defaults to `daily` only.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. First observedv0.9.5

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent, but the description adds substantial context they cannot: the pass can run for minutes and outlast the client timeout, the server completes it regardless, a run lock is held, and a retry returns 409. This is exactly the kind of timeout/locking/retry disclosure an agent needs before invoking a long destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core purpose before operational caveats. Dense but no wasted filler; the timeout/lock information is compressed effectively.

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 destructive mutation tool with no output schema, the description covers the critical behavioral risks (duration, timeout, locking, retry 409, dry-run preview). It could say more about what the pass actually rewrites in memory, but the operational picture is largely complete.

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%, so the schema already documents all four parameters including dry_run's preview behavior. The description repeats the dry_run semantics but says nothing about nightly, sources, or respect_gate, so it adds little beyond the schema. 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 (Run) and resource (manual knowledge consolidation pass), and the word 'manual' implies contrast with the automatic cron path. It does not explicitly name a sibling alternative, so it stops short of a 5.

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

Usage Guidelines3/5

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

Provides clear operational guidance for dry_run but never states when a consolidation pass is warranted versus siblings like palinode_trigger or palinode_review. Usage is implied by 'manual' rather than spelled out with conditions.

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