Palim

palim_save_context

Idempotent

Lightweight checkpoint: self-contained handoff, no transcript. Reuse session_id in this chat. Proactive after results and decisions, not only once.

Input Schema

Name	Required	Description
`tags`	No	Optional search tags.
`title`	No	Chat title when visible.
`origin`	No	human (default) or automation (hooks/cron).
`status`	No	Optional status, e.g. laufend or abgeschlossen.
`context`	Yes	Handoff another AI can continue from: goal, state, constraints, next steps.
`project`	No	Optional project name.
`created_at`	No	Optional ISO 8601 chat date from the client.
`key_topics`	No	Main topics.
`open_items`	No	Open tasks.
`session_id`	No	Stable chat ID. Reuse it so checkpoints update one row. Claude Code/Codex: claude-code-<client session id>.
`source_urls`	No	Optional URLs.
`tool_source`	No	Client: cursor, claude, chatgpt, … Optional; defaults from the MCP client name, else unknown.
`continues_from`	No	Optional session_id from palim_resume that this chat continues.
`decisions_made`	No	Decisions in this chat.
`referenced_files`	No	Relevant files.
`resolved_open_items`	No	Previously open items that are now done; quote a leading fragment.

Output Schema

Name	Required	Description	Default
`message`	Yes	Human-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / tool_source / description

Previous value: -"Client: cursor, claude, chatgpt, …"New value: +"Client: cursor, claude, chatgpt, … Optional; defaults from the MCP client name, else unknown."

changedInput schema / required

Previous value: -[
-  "context",
-  "tool_source"
-]New value: +[
+  "context"
+]

Changed14 schema fields changedAug 26, 2026

changedInput schema / properties / context / description

Previous value: -"Concise but self-contained handoff: goal, relevant background, work completed, current state, constraints, and next steps. Write it so another AI can continue without the transcript."New value: +"Handoff another AI can continue from: goal, state, constraints, next steps."

changedInput schema / properties / continues_from / description

Previous value: -"Optional. session_id of the thread this chat continues, as reported by palim_resume. Keep your own new session_id; this only records the link."New value: +"Optional session_id from palim_resume that this chat continues."

changedInput schema / properties / created_at / description

Previous value: -"Optional chat creation date from the AI client (ISO 8601)."New value: +"Optional ISO 8601 chat date from the client."

changedInput schema / properties / decisions_made / description

Previous value: -"Decisions reached in this chat."New value: +"Decisions in this chat."

changedInput schema / properties / key_topics / description

Previous value: -"Main topics covered."New value: +"Main topics."

changedInput schema / properties / open_items / description

Previous value: -"Remaining tasks or unresolved questions."New value: +"Open tasks."

changedInput schema / properties / origin / description

Previous value: -"Who produced this checkpoint. Use \"automation\" for scheduled routines, cron jobs and capture hooks — anything saved without a human in the loop. Defaults to \"human\". Automated saves are counted separately in palim_get_stats so they cannot be mistaken for real usage."New value: +"human (default) or automation (hooks/cron)."

changedInput schema / properties / referenced_files / description

Previous value: -"Relevant files or resources."New value: +"Relevant files."

changedInput schema / properties / resolved_open_items / description

Previous value: -"Open items from earlier sessions on this topic that are now DONE. Quote the wording of the item (a leading fragment is enough); it is moved out of Open Items into a dated Resolved section. Use this whenever a chat finishes something previously listed as open, otherwise the worklist keeps showing completed work."New value: +"Previously open items that are now done; quote a leading fragment."

changedInput schema / properties / session_id / description

Previous value: -"Stable chat ID, reused for every checkpoint in this chat so the record is updated instead of duplicated. In Claude Code / Codex use `claude-code-<the client session id>` — the Stop hook keeps that same row's live tail current, and sharing the ID keeps your handoff and that tail on one row. Otherwise reuse the ID returned by your first checkpoint in this chat."New value: +"Stable chat ID. Reuse it so checkpoints update one row. Claude Code/Codex: claude-code-<client session id>."

changedInput schema / properties / source_urls / description

Previous value: -"Optional chat URL and referenced URLs."New value: +"Optional URLs."

changedInput schema / properties / status / description

Previous value: -"Optional lifecycle status such as laufend or abgeschlossen."New value: +"Optional status, e.g. laufend or abgeschlossen."

changedInput schema / properties / title / description

Previous value: -"Exact chat title when visible. Omit if unavailable; Palim derives a short title from context."New value: +"Chat title when visible."

changedInput schema / properties / tool_source / description

Previous value: -"AI platform this chat originates from, for example codex, cursor, claude, chatgpt, gemini, perplexity, granola, or web."New value: +"Client: cursor, claude, chatgpt, …"

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "description": "Human-readable tool result text.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "message"
+  ],
+  "type": "object"
+}

First observedAug 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare idempotent=true, destructive=false and readOnly=false, so the safety profile is covered. The description adds real behavioral context beyond them: what is stored ('no transcript', self-contained handoff) and that repeated calls should reuse session_id to update one row rather than create duplicates.

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?

Three short fragments, no filler: what it is, the key operational constraint, and when to invoke it. Purpose and the session_id instruction are front-loaded before the timing advice.

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 an output schema present, return values need no explanation, and the schema covers all parameters. The description supplies purpose and cadence but leaves the relationship to palim_save_session, palim_checkpoint and palim_resume unstated, which matters given the crowded sibling set.

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 all 16 parameters are already documented in the schema, including the session_id reuse semantics and the origin enum. The description adds no format or syntax detail beyond what the schema provides, making the baseline 3 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?

The description states a specific action and scope: a lightweight checkpoint that produces a 'self-contained handoff, no transcript.' This distinguishes it in substance from a transcript-heavy sibling like palim_save_session, but it never names that sibling or any other, so the agent must infer the contrast from the sibling list.

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?

It gives concrete timing guidance ('Proactive after results and decisions, not only once') and an operational instruction ('Reuse session_id in this chat'), which is more than most definitions offer. It stops short of naming alternatives (palim_save_session, palim_checkpoint) or stating when not to use this tool.

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

All Palim tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.