looplens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOOPLENS_DB_PATH | No | SQLite database path | ~/.looplens/looplens.db |
| LOOPLENS_DATA_DIR | No | Base data directory | ~/.looplens |
| LOOPLENS_LOG_LEVEL | No | Log level | INFO |
| LOOPLENS_RETENTION_DAYS | No | Days before old sessions are pruned | 90 |
| LOOPLENS_LOOP_WINDOW_SIZE | No | Sliding window size for detection | 20 |
| LOOPLENS_REDACTION_ENABLED | No | Auto-redact secrets from payloads | true |
| LOOPLENS_LOOP_FREQUENCY_THRESHOLD | No | Min repeats to flag a loop | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionB | Create a new LoopLens debug session to track tool events. |
| get_sessionA | Get details for a debug session including loop count and convergence score. |
| list_sessionsA | List debug sessions with optional status filter and pagination. |
| close_sessionB | Close a debug session as completed or abandoned. |
| ingest_eventB | Ingest a single tool event into a session. |
| ingest_batchB | Ingest multiple tool events at once. |
| get_session_eventsB | Retrieve events for a session with pagination. |
| detect_loopsB | Run loop detection algorithms on a session and return detected loop patterns. |
| get_loopsC | Get all detected loop patterns for a session. |
| mark_false_positiveB | Mark a loop detection as a false positive. |
| get_convergenceB | Get convergence score for a session (computes if not cached). |
| analyze_convergence_trendC | Analyze convergence trend over time for a session. |
| export_eval_casesB | Export session data as structured eval cases for model evaluation. |
| get_diagnosticsA | Get LoopLens server diagnostics: session counts, event totals, DB path. |
| annotate_eventA | Add a key-value annotation to a specific event. |
| search_eventsC | Search events in a session by tool name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug_loop_session | Guide Claude through diagnosing and breaking a loop in a debug session |
| analyze_convergence | Analyze convergence trajectory and recommend improvements |
| generate_eval_case | Generate a structured eval case from session data |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Sessions | List of all currently active debug sessions |
| Recent Loops | The 10 most recently detected loop patterns |
| Server Diagnostics | LoopLens server stats and health metrics |
| Event Schema | JSON schema for ToolEvent ingestion format |
TDQS
Scored across 16 tools
Tools are largely distinct: session lifecycle, event ingestion/query, loop detection, convergence, and diagnostics each have clear separation. Minor overlap exists between get_session and get_convergence, but descriptions clarify their different purposes.
All tools follow a consistent verb_noun pattern with snake_case, e.g., create_session, ingest_event, detect_loops. No mixed conventions or vague verbs, making the API predictable and easy to navigate.
16 tools is slightly above the ideal 3-15 range, but each tool serves a distinct function within the domain. The count feels justified given the breadth of session management, event processing, analysis, and export capabilities.
The domain covers session lifecycle (create/get/list/close), event ingestion (single/batch), querying, annotation, loop detection, convergence analysis, and export. Lack of session update/delete is a minor gap, but core workflows are well supported.