Skip to main content
Glama

palim_checkpoint

Idempotent

Saves a short handoff of the current chat: goal, state, decisions and open items, without the transcript. Saving again with the same session_id updates the same entry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>"
    },
    "name": "palim_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional search tags.
titleNoChat title when visible.
originNohuman (default) or automation (hooks/cron).
statusNoOptional status, e.g. laufend or abgeschlossen.
contextYesHandoff another AI can continue from: goal, state, constraints, next steps.
projectNoOptional project name.
created_atNoOptional ISO 8601 chat date from the client.
key_topicsNoMain topics.
open_itemsNoOpen tasks.
session_idNoStable chat ID. Reuse it so checkpoints update one row. Claude Code/Codex: claude-code-<client session id>.
source_urlsNoOptional URLs.
tool_sourceNoClient: cursor, claude, chatgpt, … Optional; defaults from the MCP client name, else unknown.
continues_fromNoOptional session_id of the thread this chat continues.
decisions_madeNoDecisions in this chat.
referenced_filesNoRelevant files.
resolved_open_itemsNoPreviously open items that are now done; quote a leading fragment.

Output Schema

NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / continues_from / description
      Previous value: -"Optional session_id from palim_resume that this chat continues."New value: +"Optional session_id of the thread this chat continues."
  2. Changed2 schema fields changed
    • 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"
      +]
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotency and non-destructiveness; the description adds the specific mechanism — reusing session_id updates the same entry — which tells the agent the upsert key, plus the constraint that no transcript is stored and the handoff should be short. It does not cover size limits or permission requirements.

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, front-loaded with the core action and followed by the one behavioral fact an agent must know to avoid creating duplicate rows. Nothing is redundant or padded.

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, a rich 16-param schema, and an output schema, the description only needs to convey the write's purpose and the upsert rule, and it does both. The main gap is that it does not situate this tool against the sibling save/resume tools.

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, including session_id's upsert semantics. The description echoes the context field contents (goal, state, decisions, open items) but adds no syntax or format detail beyond the schema, which is the baseline case.

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 and resource — saving a short handoff of the current chat (goal, state, decisions, open items) — and adds the key differentiator 'without the transcript'. It does not explicitly name how it differs from siblings like palim_save_session or palim_save_context, so it stops short of a 5.

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

Usage Guidelines3/5

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

The phrase 'handoff another AI can continue from' and 'without the transcript' imply the checkpoint use case, and the upsert note implies repeated saving is fine. However, there is no explicit when-to-use vs when-to-use-an-alternative guidance against the several save/search siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.