Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_lint

Read-onlyIdempotent

Scan memory for health issues: orphaned or stale files, missing frontmatter, contradictions. Returns a report without modifying files; optionally proposes consolidation operations.

Instructions

Scan memory for health issues: orphaned files, stale active files (>90 days), missing frontmatter fields, and potential contradictions. Returns a report without modifying files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposeNoAlso translate the deterministic findings into proposed consolidation operations, each with its rationale and the finding it came from. Advisory: this tool never applies them — run `palinode lint --apply` to let the executor act.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.1
    • addedInput schema / properties / propose
      Added value: +{
+  "description": "Also translate the deterministic findings into proposed consolidation operations, each with its rationale and the finding it came from. Advisory: this tool never applies them — run `palinode lint --apply` to let the executor act.",
+  "type": "boolean"
+}
  2. First observedv0.9.5

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds value beyond that: it confirms 'Returns a report without modifying files' and discloses the concrete staleness threshold (>90 days), a behavioral detail absent from the annotations.

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?

Two tight sentences, front-loaded with the scan target and its checks, then the non-mutating guarantee. The enumerated issue list is dense but each item carries meaning; no filler.

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

Completeness3/5

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

For a read-only lint tool with one optional param and no output schema, the description covers purpose, scope, and non-mutation adequately. But given a crowded 30-sibling namespace with three overlapping 'doctor'-style tools, it omits the differentiation an agent needs to disambiguate.

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 'propose' parameter is documented richly in the schema itself (including the advisory note that nothing is applied). The description does not mention 'propose' or the report's structure, but with full schema coverage the baseline of 3 is appropriate.

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 ('Scan') and resource ('memory') and enumerates the exact health classes it detects (orphaned files, stale >90d, missing frontmatter, contradictions), so the intent is unambiguous. However, it never distinguishes itself from close siblings like palinode_doctor, palinode_doctor_deep, or palinode_orphan_repair, leaving the agent to guess which check-tool it wants.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and with siblings named palinode_doctor, palinode_doctor_deep, and palinode_orphan_repair, the omission is material. The description only says what it scans, not when an agent should pick lint over the doctor family.

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