Skip to main content
Glama

palim_resume

Read-onlyIdempotent

Returns the user's most recently updated Palim thread as a handoff: state, decisions and open items. Useful at the start of a new chat; the thread may be unrelated to the current request. Project filter is case-insensitive.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "palim_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoOptional: only consider threads belonging to this project (case-insensitive; Logisoft ≡ logisoft).
tool_sourceNoOptional: only consider threads from one client (cursor, claude, codex, chatgpt, ...).
within_hoursNoOptional: ignore threads older than this many hours. Omit to always return the latest thread.
include_messagesNoOptional: append the tail of the transcript when the thread has stored messages. Default false.

Output Schema

NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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)."
  2. 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"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is narrower. It adds real value by describing the returned artifact as a handoff containing state, decisions and open items, and by warning that the resumed thread may be irrelevant to the current request. It does not say what happens when no qualifying thread exists, which is the one remaining behavioral gap.

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?

Two sentences, front-loaded with what is returned, followed by the relevance caveat and the filter note. It is efficient, though the case-insensitive remark duplicates the schema and is the weakest sentence in the block.

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?

With four fully documented optional parameters and an output schema, the description need not explain return values or field formats. It covers purpose, content of the handoff, and the relevance caveat; only the empty-result case is unaddressed.

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 filters are already documented in the schema, including the case-insensitive project matching. The description only restates the case-insensitivity note and adds no syntax, precedence, or interaction detail (e.g. how within_hours combines with project). Baseline 3 is appropriate.

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?

The description gives a specific verb and resource ('Returns the user's most recently updated Palim thread') plus the payload shape (state, decisions, open items), which is enough to separate it from generic retrieval siblings like palim_get_context or palim_search. It stops short of naming an alternative, but the scope is unambiguous.

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?

It states a concrete usage occasion ('Useful at the start of a new chat') and a genuine caution ('the thread may be unrelated to the current request'), which helps the agent decide whether the result is worth trusting. It does not name a sibling to use instead when the user's request is topic-specific, so guidance is clear but not complete.

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.