Palim

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

TableJSON Schema

Name	Required	Description
`title`	Yes	Session title. Reuse across saves; else the exact chat title from the client UI.
`summary`	No	Full-conversation summary. Required arrays may be empty.
`messages`	Yes	Messages to save (role + content). When appending, only unsaved messages.
`metadata`	No	Session metadata. tool_source is required.
`overwrite`	No	Replace all existing messages instead of appending. Default: false.
`created_at`	No	Optional ISO 8601 creation date from the AI client (new sessions only).
`session_id`	No	Session id. Reuse across saves in this chat; else from chat URL or a new UUID.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 30, 2026
RemovedAug 26, 2026

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.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, non-idempotent, non-read-only, so the safety profile is covered. The description still adds real value the annotations do not: data-handling exclusions (minors, PHI, PCI, adult content), the instruction to request redaction before saving, and the append-vs-replace workflow. It does not spell out the consequence of overwrite=true, but that is documented in the schema.

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?

Front-loaded with the core purpose, then routing, then compliance, then append mechanics. Every sentence carries actionable information with no filler; it is dense but not padded.

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?

Given a 7-parameter nested schema with 100% coverage, annotations, and a declared output schema, this description supplies the remaining pieces an agent needs: compliance exclusions, the sibling it should prefer, and the exact append workflow. Nothing required to invoke it correctly is missing.

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% and nested objects are fully documented, so the baseline is 3. The description reinforces that summary and metadata.tool_source must always be complete and hints at session_id/title reuse, but adds little beyond what the schema already specifies for each field.

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?

The opening sentence states a specific verb and resource — save or append a full chat transcript (messages + summary) — and immediately distinguishes the operation from siblings by naming palim_save_context and the two update tools. An agent can tell exactly what this tool writes and what it does not.

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?

Explicit routing rules are given: prefer palim_save_context for compact handoffs, use palim_update_session_metadata / palim_update_session_references for metadata-only or URL updates. It also gives the concrete append procedure (reuse session_id + title, fetch existing messages first, send only new ones), which is unambiguous when-to-use/when-not guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.