Skip to main content
Glama
Sign In
SuperSkill

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resume

Read-only

Retrieve recent sessions, interrupted work, and in-progress tasks to continue where you left off. Call at session start for suggested next steps and prior context.

Instructions

Get resume context for continuing work — recent sessions, interrupted work, in-progress tasks, suggested next steps. Call this at session start to understand what happened before.

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": "resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent sessions to show (default 5)
formatNoOutput format (default markdown)
projectNoProject slug (auto-detected if omitted)
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. First observedv0.6.1

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, so the safety burden is lifted. The description adds the content scope of the result but says nothing about behavior beyond that — no auth needs, data source, cost, or pagination/limit behavior beyond what the schema states.

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 tightly packed sentences with zero filler; the purpose and the trigger condition are both front-loaded and every clause 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?

With no output schema, the description usefully enumerates what the tool returns (sessions, interrupted work, tasks, next steps), which is exactly the burden it must carry. The main gap is the absence of routing guidance relative to the sibling 'session' tool.

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 (limit, format, project, workspace_path) are already documented in the schema. The description adds no additional parameter meaning, so the baseline of 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 ('Get resume context') and enumerates exactly what that context contains — recent sessions, interrupted work, in-progress tasks, suggested next steps. It distinguishes itself from generic tools, though it never explicitly contrasts with the similarly-named sibling 'session'.

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?

Explicitly says when to call it: 'Call this at session start to understand what happened before.' That is a clear usage context, but there is no when-not guidance and no named alternative (e.g. 'session' or 'project_context') to route between.

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