Skip to main content
Glama
LCV-Ideas-Software

cross-review

by LCV-Ideas-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Recover Interrupted Sessions

session_recover_interrupted
Idempotent

Mark unfinished sessions with stale in-flight rounds as recovered after a host restart so they can be resumed explicitly. Works only for sessions you own.

Instructions

Mark unfinished sessions with stale in-flight rounds as recovered after a MCP host restart so they can be resumed explicitly. Requires your own verified capability token, and recovers only the sessions you own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callerYes
response_formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.4.18
    • removedInput schema / properties / caller / default
      Removed value: -"operator"
    • changedInput schema / properties / caller / enum
      Previous value: -[
-  "codex",
-  "claude",
-  "gemini",
-  "deepseek",
-  "grok",
-  "perplexity",
-  "operator"
-]New value: +[
+  "codex",
+  "claude",
+  "gemini",
+  "deepseek",
+  "grok",
+  "perplexity"
+]
    • addedInput schema / required
      Added value: +[
+  "caller"
+]
  2. First observedv4.4.8

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, and the description does not contradict them. It adds useful behavioral context: only stale in-flight rounds are affected, only the caller's own sessions are recovered, and a verified capability token is required.

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?

Two focused sentences: the first front-loads the core action and context, the second adds necessary constraints. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what, when, and preconditions, which is largely sufficient for a simple two-parameter tool. However, it does not define what qualifies as 'stale,' explain the return/output behavior, or clarify how response_format affects the result, and there is no output schema to fill that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention the caller or response_format parameters at all. The enum values are somewhat self-explanatory, but the description adds no guidance on how these parameters affect recovery or the output.

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 description states a specific action with a concrete resource: marking unfinished sessions with stale in-flight rounds as recovered after an MCP host restart. This clearly distinguishes the tool from sibling list/read/poll/finalize 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?

It gives clear context for when to use the tool (after a host restart, before explicit resumption) and adds restrictive conditions (owned sessions only, verified capability token required). It does not name alternative tools or explicitly state when not to use it, but the context is sufficient.

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

Deploy Server

Other Tools