unstuck-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNSTUCK_DIR | No | Where attempt history is stored | <cwd>/.unstuck |
| UNSTUCK_THRESHOLD | No | How many failed attempts before blocking (3rd attempt = 1st time blocked) | 2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| report_attemptA | Report that a fix attempt for an error/bug just failed. Returns whether this exact problem has been tried before and whether you're now required to use your web search tool before retrying. Call this immediately after any failed fix, before writing more code. |
| confirm_searchA | Call this after using your own web search tool to look up an error that report_attempt flagged as blocked. Clears the block and lets you resume fixing, now informed by current information instead of a repeated guess. |
| loop_statusA | View all currently tracked failed-attempt histories for this project, sorted by repeat count. Useful for checking what's been stuck. |
| reset_loopA | Clear tracked attempt history so a problem is no longer flagged as a repeat. Pass an error_signature to clear just that one, or clear_all=true to wipe everything for this project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: reporting a failed attempt, confirming a search, viewing status, and resetting state. No overlap or ambiguity between them.
Three tools follow the verb_noun pattern (report_attempt, confirm_search, reset_loop), while loop_status is noun_noun but still reads as a status query. Minor deviation but overall predictable.
Four tools is well-scoped for this narrow domain of tracking and managing failed-attempt loops. No redundant tools, each earns its place.
The domain is fully covered: report failures, unblock after search, view history, and reset. No obvious gaps for the stated purpose.