Skip to main content
Glama
Pickle-Pixel

HydraMCP

by Pickle-Pixel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

session_recap

Read past Claude Code sessions and produce a structured recap to restore project context, highlighting state, built features, key decisions, errors, and file map.

Instructions

Read previous Claude Code sessions from disk and generate a smart-sized recap using a large-context model. Claude never sees the raw session data — only the distilled summary.

OUTPUT: Returns markdown starting with "## Session Recap" containing sections: Project State, What Was Built, Key Decisions, Errors Resolved, Unfinished/In Progress, File Map. Empty sections are omitted. Output size is auto-calculated (1K-30K tokens) based on session density.

WHEN TO USE: At the start of a new session when the user asks to restore context, recall previous work, or continue where they left off.

FAILURE MODES:

  • "No recent project detected" + list of available projects → Retry with an explicit project path from the list.

  • "Project directory not found" + available projects → The project path was misspelled or encoded wrong. Retry with a path from the available list.

  • "No session files found" → The project directory exists but has no sessions. Try a different project.

  • "No models available" → CLIProxyAPI or Ollama is not running. Tell the user to start their model provider.

  • "Session Recap Failed" with error details → Both summarization passes failed. Retry with fewer sessions (sessions=1) or a different model.

  • "Triage Only" heading → Partial success. The triage pass worked but the full recap failed. The output still contains useful structured data. Do not retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionsNoNumber of recent sessions to recap (default: 3)
projectNoProject path to recap, e.g. 'C:\\Users\\Beast\\Documents\\GitHub\\MyProject'. Auto-detects most recent project if omitted.
focusNoOptional focus area to filter both triage and recap, e.g. 'auth implementation' or 'database migration'. When set, only events related to this topic are counted and summarized.
modelNoModel to use for recap. Should be a large-context model like Gemini. Auto-picks if omitted.
max_summary_tokensNoOverride the auto-calculated summary budget (in tokens). Auto-calculation ranges from 1K to 30K based on session density.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that Claude never sees raw data, details output sections, and enumerates failure modes. Lacks explicit statement that it is a read-only operation, but this is implied by the purpose.

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?

Well-structured with clear sections (OUTPUT, WHEN TO USE, FAILURE MODES). Slightly verbose due to extensive failure mode details, but each sentence adds value. Front-loaded with essential purpose.

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 no output schema and no annotations, the description covers purpose, usage, output format, and failure modes comprehensively. It could potentially include more on return value structure, but the markdown format is sufficiently described.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant value beyond schema: clarifies auto-detection for project, auto-calculation for max_summary_tokens, and purpose of focus. Provides concrete examples (e.g., 'auth implementation').

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 clearly states it reads previous sessions and generates a recap. The verb 'Read' and 'generate' along with the resource 'previous Claude Code sessions' precisely define the tool's action, distinguishing it from sibling tools like analyze_file or ask_model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes an explicit 'WHEN TO USE' section with clear scenarios (start of session, restore context, continue work). Also provides failure modes with retry actions, which guide the agent on next steps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pickle-Pixel/HydraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server