Palim

palim_resume

Read-onlyIdempotent

Continue the user's most recent Palim thread. Call first in a new chat, no args. Ignore the result if it is unrelated. Project filter is case-insensitive and returns the most recently updated match.

Input Schema

TableJSON Schema

Name	Required	Description
`project`	No	Optional: only consider threads belonging to this project (case-insensitive; Logisoft ≡ logisoft).
`tool_source`	No	Optional: only consider threads from one client (cursor, claude, codex, chatgpt, ...).
`within_hours`	No	Optional: ignore threads older than this many hours. Omit to always return the latest thread.
`include_messages`	No	Optional: append the tail of the transcript when the thread has stored messages. Default false.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / project / description

Previous value: -"Optional: only consider threads belonging to this project."New value: +"Optional: only consider threads belonging to this project (case-insensitive; Logisoft ≡ logisoft)."

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

Behavior3/5

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

Annotations already disclose readOnly, idempotent, and non-destructive behavior, so the description does not need to restate them. It adds useful nuance: the result may be unrelated and should be ignored, and project matching is case-insensitive and returns the most recently updated match. This adds value but no deeper behavioral detail.

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?

Four short sentences carry distinct, useful guidance with no filler. The main purpose is front-loaded, followed by call timing and behavioral caveats. Every sentence earns its place.

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?

Given the output schema, annotations, and full parameter descriptions, the tool is well documented. The description covers invocation timing and result handling, while schema covers parameter details. It is complete enough for an agent to call correctly on first attempt.

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 four parameters are individually documented. The description reinforces the project parameter's case-insensitive behavior and the default no-args call pattern, but adds little beyond what the schema already provides. Baseline 3 applies.

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?

Description states a specific verb ('Continue') and resource ('user's most recent Palim thread'), making the tool's role immediately clear. It also distinguishes this from sibling tools such as palim_search and palim_save_session, so agents can select it without opening schemas.

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 explicit invocation guidance: call first in a new chat with no args, and tells the agent to ignore unrelated results. It does not explicitly name alternatives or when-not-to-use, but the contextual cue is strong enough for correct selection.

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.