Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_resolve

Read-onlyIdempotent

Get the current answer to a question or record from memory, resolving standing assertions, replacements, conflicts, and unknowns instead of a list of search hits.

Instructions

Ask what memory holds RIGHT NOW about a question, or about one record. Returns the assertions that stand (with their evidence and source revisions), what replaced what, conflicts with every side intact, and what is explicitly unknown. Use instead of palinode_search when you want the current answer rather than a list of hits. Read-only; a tight budget can shrink the answer but never turns a conflict into a settled one. Retired records are left out, as in search, unless include_retired=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoExact memory ref (path without .md), e.g. 'decisions/db'.
queryNoNatural-language question. Give this or `ref`.
intentNoWhat to answer. Only current state is supported.current_state
contextNoRefs you already hold; each is checked, not assumed current.
max_charsNoMax characters in the answer (default 2000).
max_itemsNoMax units in the answer (default 8).
include_retiredNoAlso return retired records (archived, superseded, retracted, expired), labelled as history. Off by default, as in search.
include_other_projectsNoAlso return records tagged to other projects, each labelled with its project. Off by default: a project-scoped request leaves them out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.22.0
    • addedInput schema / properties / include_other_projects
      Added value: +{
+  "default": false,
+  "description": "Also return records tagged to other projects, each labelled with its project. Off by default: a project-scoped request leaves them out.",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_retired
      Added value: +{
+  "default": false,
+  "description": "Also return retired records (archived, superseded, retracted, expired), labelled as history. Off by default, as in search.",
+  "type": "boolean"
+}
  2. Addedv0.20.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds non-obvious behavior: budget constraints may shrink the answer but 'never turn a conflict into a settled one', retired records are excluded by default, and it spells out the return contents (assertions, evidence, source revisions, replacement chains, conflicts, unknowns).

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?

The answer content and the differentiator are front-loaded, and every sentence carries information. The middle sentences are somewhat dense and list-heavy, but nothing is padding.

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 read tool with no output schema, the description covers what is returned, the default exclusions, the budget caveat, and the ref-vs-query distinction. An agent has enough to call it correctly without further inspection.

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 baseline is 3. The description adds meaning by explaining that ref targets 'one record' while query targets 'a question', and by reiterating the include_retired default, going slightly beyond the schema text.

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?

The description states a specific verb+resource ('resolve what memory holds RIGHT NOW') and explicitly contrasts itself with palinode_search. An agent can distinguish it from the 35+ siblings by the 'current answer vs list of hits' framing.

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

Usage Guidelines5/5

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

It names the alternative (palinode_search) and the condition that selects this tool ('when you want the current answer rather than a list of hits'). It also states the ref/query choice and the include_retired behavior, leaving little 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