Skip to main content
Glama

palim_save_session

Destructive

Saves or appends a full chat transcript with its summary. Not for personal data of children under 16 (or a higher local consent age), HIPAA PHI, PCI payment card data or adult content. Appending with the same session_id adds the new messages to the existing session.

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": {
      "title": "<title>",
      "messages": "<messages>"
    },
    "name": "palim_save_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesSession title. Reuse across saves; else the exact chat title from the client UI.
summaryNoFull-conversation summary. Required arrays may be empty.
messagesYesMessages to save (role + content). When appending, only unsaved messages.
metadataNoSession metadata. tool_source is required.
overwriteNoReplace all existing messages instead of appending. Default: false.
created_atNoOptional ISO 8601 creation date from the AI client (new sessions only).
session_idNoSession id. Reuse across saves in this chat; else from chat URL or a new UUID.

Output Schema

NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. 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"
      +}
  4. 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 destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is known. The description reinforces the important behavioral trait that reusing session_id appends rather than replaces, but it does not say what overwrite=true actually destroys, whether unknown metadata fields are merged or dropped, or what happens on a conflicting title/session_id. With annotations carrying the basics, this is a modest but real addition.

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?

Three sentences, no filler, with the core action and the append rule front-loaded. The middle sentence is a dense compliance block but every clause earns its place and nothing is restated redundantly.

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?

For a 7-parameter mutation tool with nested objects, an output schema, and full annotation coverage, the description supplies the decision-critical facts: append vs. overwrite semantics and content-type exclusions. Only minor gaps remain around merge behavior for metadata and idempotency expectations on repeated saves.

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 seven parameters including nested summary and metadata fields are already documented in the schema. The description only restates the session_id append semantics and adds no format, constraint, or edge-case guidance beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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 or appends a full chat transcript with its summary') and even distinguishes the two write modes (save vs. append) in one sentence. It stops short of differentiating itself from close siblings like palim_save_context or palim_checkpoint, so an agent must infer the boundary from names alone.

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?

Gives clear operational guidance: reuse the same session_id to append, and when appending only unsaved messages should be sent. It also sets explicit content exclusions (minors' data, HIPAA PHI, PCI card data, adult content), which is real when-not-to-use guidance. It never names a sibling alternative for the cases this tool is not meant to handle, so routing 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.