Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_list

Read-onlyIdempotent

List memory files by category, core status, or frontmatter filters to browse stored memories before reading or searching.

Instructions

List memory files, optionally filtered by category, core status or frontmatter. Use to browse what memories exist before reading or searching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whereNoFrontmatter filters as key=value (e.g. status=open); all must match.
categoryNoFilter by category: people, projects, decisions, insights, research
core_onlyNoIf true, only return files with core: true in frontmatter
include_inboxNoAlso list inbox/, where ActionItems are saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.23.0
    • addedInput schema / properties / include_inbox
      Added value: +{
+  "default": false,
+  "description": "Also list inbox/, where ActionItems are saved.",
+  "type": "boolean"
+}
    • addedInput schema / properties / where
      Added value: +{
+  "description": "Frontmatter filters as key=value (e.g. status=open); all must match.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv0.9.5

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that filters are optional; it says nothing about return volume, pagination, or that inbox entries are hidden unless include_inbox is set. Adequate but not rich.

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 sentences, no filler: the operation is stated first and the usage cue second. Every clause earns its place.

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?

With annotations covering safety and the schema covering all parameters, the description supplies the missing purpose and usage framing. No output schema exists, so return shape is undescribed, but for a simple read-only list tool this is a minor gap.

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 the schema already documents all four parameters including enum values and defaults. The description restates the same three filter axes (category, core status, frontmatter) without adding syntax or examples, so the 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 (List) and resource (memory files) plus the optional filter dimensions, which distinguishes it from mutating siblings. It implies differentiation from palinode_read/palinode_search by positioning itself as the browse step before them, though it does not name those siblings explicitly.

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?

"Use to browse what memories exist before reading or searching" gives clear when-to-use context and implicitly routes the agent to read/search for targeted retrieval. There is no explicit when-not or named-alternative clause, so it falls short of a 5.

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