MCP server to search, read, and tail past and live Claude Code sessions
Four read-only tools with clear verb-noun naming (list_, search_, get_, tail_). All have descriptions (avg ~100 chars, within baseline 34-392). Input schemas present with types and descriptions for all parameters. However, output schemas are entirely undocumented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., 'session_id' accepts 'ID or prefix' but no regex/length guidance). No error handling guidance. No pagination metadata (limit/offset/total) documented. Tool descriptions are functional but generic; they don't explain WHEN to use each tool vs. alternatives or what downstream tools need.
Retrieve the full transcript of a session by ID or ID prefix
List Claude Code sessions, optionally filtered by project, activity status, or time range
Search across all sessions for a query string, returning matching sessions with snippets
Stream the most recent messages from a live or recent session
Output schemas completely undocumented. LLMs cannot predict response structure (fields, types, nesting). Rubric baseline: 100% of A+ tools have documented return types.
Parameter 'session_id' accepts 'ID or prefix' but lacks format constraints (length, regex, character set). Rubric: 'When a parameter has a regex pattern, length limit, or character restriction, state it in the description.'
No pagination metadata documented (total count, next_cursor, or offset). Rubric: 'Tools returning lists should accept page/offset and limit parameters and return a total count or next_cursor.'
No error handling guidance. Rubric: 'Error responses must tell the LLM what to do next.' E.g., if session_id not found, should LLM retry with prefix search or call list_sessions?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Tool descriptions lack WHEN/WHY guidance. 'List Claude Code sessions' doesn't explain when to call list_sessions vs. search_sessions, or what fields the response contains for downstream chaining.