Skip to main content
Glama

palim_save_context

Idempotent

Saves a self-contained handoff of the current chat 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_save_context"
  }
}

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. Changed14 schema fields changed
    • 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, …"
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "message": {
      +      "description": "Human-readable tool result text.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world write. The description adds real value by naming the update key (session_id) and the payload scope (no transcript), but it does not say whether resaving overwrites or preserves previously stored fields, which is the key ambiguity for an idempotent write.

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 tight sentences, zero filler, with the content scope front-loaded and the update rule second. Nothing repeats the name or title.

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?

Output schema exists, so return values need not be explained, and 100% schema coverage handles the 16 parameters. What remains thin is disambiguation from the several save/checkpoint siblings in the catalog, though the 'handoff, not transcript' framing does much of that work implicitly.

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% across all 16 parameters, including clear per-field descriptions for context, session_id, and resolved_open_items, so the schema carries the semantic load. The description adds no parameter-level detail beyond the schema, which is the baseline 3 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: saves a self-contained handoff of the current chat, explicitly excluding the transcript. That distinguishes the payload from a raw transcript dump, but the description never names or contrasts the obvious sibling palim_save_session or palim_checkpoint, so an agent must still infer the difference.

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 upsert rule ('saving again with the same session_id updates the same entry') gives useful when-to-reuse guidance, but there is no explicit statement of when to choose this over palim_save_session or palim_checkpoint, and no prerequisites. Usage is implied rather than directed.

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.