Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_restore

Idempotent

Bring an archived memory back into default recall. Reverses archiving by flipping status to active, dropping superseded_by, recording provenance, and committing.

Instructions

Bring one archived memory back into default recall — the inverse of palinode_archive for every archive path (on-demand, forget request, TTL expiry, consolidation). Flips status back to active, drops superseded_by, records restored_at / restored_from provenance and a history line, and commits. Does not un-strike retraction markers (use palinode_unretract) or re-enable triggers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoWhy this memory is being restored (kept in the audit trail).
dry_runNoPreview what would change, the retained copies and the recovery command; write nothing.
file_pathYesArchived memory file path (e.g., 'insights/retired-finding.md')

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. Addedv0.17.0

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 (idempotent=true, destructive=false, readOnly=false) by disclosing the exact state changes: status flipped to active, superseded_by dropped, restored_at/restored_from provenance plus a history line, and a commit. It also states the boundary conditions (no retraction un-striking, no trigger re-enabling).

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?

Dense but front-loaded: the core action and its inverse relationship lead, followed by state effects and exclusions. No filler sentences.

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

Completeness5/5

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

For a mutation tool with no output schema, the description fully covers the state transitions, provenance recording, atomic commit, and edge cases an agent must understand before calling. Nothing material is missing.

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 description coverage is 100%, so dry_run and reason are already documented in the schema. The description adds no per-parameter syntax or meaning beyond the schema baseline, which is expected here.

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 ('Bring one archived memory back into default recall'), gives the scope ('one'), and frames it as the inverse of palinode_archive across every archive path. An agent can distinguish it from siblings without opening a 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?

Explicitly names the sibling for a related-but-different case ('Does not un-strike retraction markers (use palinode_unretract)') and clarifies it won't re-enable triggers. The when-to-use case is implied by 'inverse of palinode_archive for every archive path' rather than stated as a trigger, but routing is clear.

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