palinode

palinode_archive_expired

DestructiveIdempotent

Archive expired ephemeral memories to keep default recall clean while preserving data on disk. Use dry-run to preview changes before applying.

Instructions

Archive ephemeral memories whose expires_at has passed (ADR-015 §2.3 TTL regime). Deterministic + idempotent — flips expired memories to status: archived so they drop out of default recall while staying on disk. Set dry_run=true to preview.

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": "palinode_archive_expired"
  }
}

Input Schema

Name	Required	Description	Default
`dry_run`	No	Preview which memories would be archived without writing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.5Jul 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Expands on annotations: specifies deterministic, idempotent (consistent with idempotentHint), effect on status, persistence on disk, and dry_run preview. No contradiction with destructiveHint=true. Adds context beyond annotations.

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?

Two concise sentences front-loading the action. Every sentence provides essential info: what, effect, condition, and usage tip. No wasted words.

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?

Given no output schema and simple mutation, description fully covers purpose, behavior, and parameter. Return value not needed; tool side effects are clear.

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?

Parameter dry_run is 100% schema-covered with description. Tool description repeats schema description without adding new meaning. Baseline 3 applies as schema does the heavy lifting.

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?

Explicitly states it archives ephemeral memories with expired expires_at, referencing ADR-015. Distinguishes from sibling palinode_archive by specificity to TTL regime. Clear verb+resource scope.

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?

Clearly indicates when to use (expired memories). Implicitly distinguishes from palinode_archive (non-expired/memories), but lacks explicit exclusion or mention of alternatives.

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