Skip to main content
Glama
Sign In
palinode

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_resolve

Read-onlyIdempotent

Answer what memory currently holds for a question or record: return standing assertions, evidence, replacements, conflicts, and unknowns instead 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

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
promptNoShape a raw user prompt for recall.
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. Changed1 schema field changedv0.23.0
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Shape a raw user prompt for recall.",
+  "type": "boolean"
+}
  2. 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"
+}
  3. Addedv0.20.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds meaningful traits beyond them: the shape of the returned set, that a budget 'can shrink the answer but never turns a conflict into a settled one', and the default exclusion of retired records. This is exactly the extra context structured fields don't carry, and it does not contradict 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tightly packed sentences, front-loaded with what the tool does, then the sibling alternative, then behavioral caveats. Every sentence earns its place with no filler.

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?

There is no output schema, so the description must carry the return shape, and it does: standing assertions with evidence and source revisions, replacement chains, intact conflicts, and explicit unknowns. Combined with full schema coverage of the parameters, an agent has everything needed to call it correctly.

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 schema documents all nine parameters and the baseline would be 3. The description nevertheless adds real meaning: it maps ref/query to 'a question, or about one record', explains the budget behavior behind max_chars/max_items, and reinforces include_retired's default-off semantics.

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+resource+scope ('Ask what memory holds RIGHT NOW about a question, or about one record') and spells out the return content (assertions that stand, replaced-by, conflicts, unknowns). It explicitly names the sibling it differs from (palinode_search), so an agent can distinguish it without opening either schema.

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?

Gives an explicit when-to-use rule and names the alternative: 'Use instead of palinode_search when you want the current answer rather than a list of hits.' It also states the conditional default for retired records, leaving nothing 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