Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_archive

DestructiveIdempotent

Retire a wrong or obsolete memory by marking it archived, removing it from default recall while keeping it auditable. Optionally name a replacement to supersede it.

Instructions

Retire one specific memory that is wrong or obsolete. Sets status: archived so it leaves default recall, records the reason in the file's history sibling, and commits — never hard-deletes, so the content stays auditable. Pass superseded_by to name the memory that replaces it (a SUPERSEDE rather than a plain archive). Use this instead of re-saving a memory with a hand-written tombstone body: that leaves the wrong content live in search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoWhy this memory is being retired (kept in the audit trail).
dry_runNoPreview what would change, the retained copies and the recovery command; write nothing.
file_pathYesMemory file path (e.g., 'insights/stale-finding.md')
superseded_byNoSlug or path of the memory that replaces this one. Omit for a plain archive with no successor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.22.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": false,
+  "description": "Preview what would change, the retained copies and the recovery command; write nothing.",
+  "type": "boolean"
+}
  2. First observedv0.9.5

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it specifies the exact state change (sets status: archived), the effect (leaves default recall), where the reason is recorded (the file's history sibling), that it commits, and that it never hard-deletes so content stays auditable. The destructiveHint=true annotation is clarified rather than contradicted — this is soft, auditable mutation.

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 sentences, front-loaded with the core action and each sentence carrying distinct content (purpose, behavior, usage). Tight and well-structured, with only minor redundancy between the behavior and usage sentences.

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 4-parameter mutation tool with no output schema, the description covers the state change, the retention guarantee, the audit-trail behavior, and the alternative to avoid. An agent has enough to call it correctly; the main unstated item is what the tool returns on success or failure.

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

Parameters4/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 (baseline 3). The description adds conceptual meaning on top — superseded_by turns a plain archive into a SUPERSEDE, and reason is framed as part of the audit trail — which lifts it above the baseline.

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?

States a specific verb and resource — 'Retire one specific memory that is wrong or obsolete' — and scopes it to a single memory, which distinguishes it from the bulk sibling palinode_archive_expired. An agent can identify what the tool does 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 Guidelines4/5

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

Gives explicit when-to-use guidance and an alternative workflow ('Use this instead of re-saving a memory with a hand-written tombstone body'). However, the alternative named is a manual pattern rather than the actual sibling tools (palinode_save, palinode_archive_expired, palinode_forget_withdraw), so routing among siblings is left partly to inference.

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