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

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

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes beyond that by disclosing that the returned thread may be unrelated and should be discarded, and that the project filter matches to the most recently updated thread — useful behavior an agent would otherwise have to infer.

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?

Four short sentences, front-loaded with purpose and the calling instruction, with zero padding. The final sentence on project filtering partly duplicates the schema description, costing a bit of density.

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?

An output schema exists, so return-value explanation is unnecessary, and all four params are schema-documented. The description covers the primary calling pattern and a fallback rule; what's left out (no-thread behavior, how the resume interacts with session state) is minor for a read-only resumption helper.

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 optional params are already documented. The description restates the project filter's case-insensitive, most-recently-updated matching (which the schema already says) and says 'no args', adding little beyond the schema, so baseline 3 applies.

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+resource: 'Continue the user's most recent Palim thread.' The scope ('most recent') is precise, but it never names a sibling (e.g., palim_get_context, palim_search) to distinguish itself from the other thread/context retrieval tools.

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?

'Call first in a new chat, no args' gives explicit timing guidance and a calling pattern, and 'Ignore the result if it is unrelated' tells the agent how to handle an off-target result. No alternatives or when-not-to-use conditions are named, so it stops short of a 5.

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

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.