Skip to main content
Glama

Palim

by io.github.joleschmidt
OverviewDiscussionsAdmin

palim_save_session

Destructive

Save or append a full chat transcript (messages + summary). Exclude children's personal data under 16/higher consent age, HIPAA PHI, PCI payment card data, and adult content; request redaction before saving. Prefer palim_save_context for compact handoffs. For metadata-only or URL updates use palim_update_session_metadata / palim_update_session_references. When appending: reuse session_id + title, fetch existing messages first, send only new ones. Always pass a complete summary and metadata.tool_source.

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

A4.9/5.0
Behavior5/5

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

Annotations only flag destructiveHint/openWorldHint/readOnlyHint; the description goes well beyond by defining what is destroyed (overwrite replaces all existing messages vs. append), mandating pre-save redaction, and enumerating prohibited content classes (under-16, HIPAA PHI, PCI, adult content). That is substantive behavioral context an agent could not derive from annotations or schema.

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?

Purpose is front-loaded, then routing, then compliance, then append procedure — each sentence carries distinct operational value with no restatement of the name or schema text.

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?

For a destructive, nested-schema, multi-mode save tool with an output schema present, the description covers mode selection (append vs overwrite), call sequencing, compliance preconditions and sibling routing without needing to describe return values.

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 already documents title, summary shape, messages, metadata and overwrite; baseline is 3. The description adds cross-call semantics the schema does not carry — reuse session_id/title across saves, fetch existing messages before appending, and always supply a complete summary plus metadata.tool_source — which is genuinely useful but partial.

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?

Opens with a specific verb+resource pair ('Save or append a full chat transcript') and immediately scopes what the resource contains (messages + summary). It explicitly distinguishes itself from palim_save_context, palim_update_session_metadata and palim_update_session_references, so an agent can route without opening a 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 explicit when-to-use alternatives ('Prefer palim_save_context for compact handoffs', 'For metadata-only or URL updates use palim_update_session_metadata / palim_update_session_references') plus the append recipe (reuse session_id + title, fetch existing messages first, send only new ones). Nothing is left to inference.

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

All Palim toolsInspect
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.

Resources