get_error_details
Analyze a specific error message to identify its root cause, receive actionable resolution steps, and detect recurring patterns.
Instructions
get detailed error analysis
Use this AFTER getting recent errors when you need actionable solutions and root cause analysis.
WHEN TO USE:
You got error logs but need to understand WHY it happened
You need specific steps to fix the problem
The same error occurred multiple times (pattern analysis)
You need stack traces for deeper debugging
WHAT THIS TOOL DOES: ✅ Identifies ROOT CAUSE (not just symptoms) ✅ Provides ACTIONABLE steps to fix the issue ✅ Finds RELATED errors to spot patterns ✅ Analyzes if error is recurring (warns against pointless retries)
WORKFLOW:
Get recent errors using get_recent_errors
Copy the error message you want to analyze
Call THIS tool with that error message
Get: Root cause + Specific fix actions + Pattern warnings
BUILT-IN ERROR PATTERN RECOGNITION:
Permission/Auth errors -> Suggests checking credentials, scopes, permissions
Rate limit errors -> Suggests backoff strategies, caching, tier upgrades
Timeout errors -> Suggests increasing timeout, chunking requests
Not found errors -> Suggests verifying IDs, checking deletions
Network errors -> Suggests connectivity checks, firewall settings
Invalid input errors -> Suggests validation, format checking
Server errors (5xx) -> Identifies as provider-side, suggests waiting
EXAMPLE USE CASE: Error: "Failed to send message" → Get recent errors: shows "missing_scope: chat:write" → Analyze error: ROOT CAUSE = "Permission error" ACTIONS = ["Add chat:write OAuth scope", "Regenerate token"] → Fix immediately instead of retrying 4+ times!
Args:
server_name (string): Name of the MCP server where error occurred
error_message (string): The error message or pattern to search for
include_stack_trace (boolean): Include full stack traces (default: false)
response_format ('markdown' | 'json'): Output format (default: 'markdown')
Returns: For Markdown format: Human-readable analysis with root cause and action steps For JSON format: Structured data with schema: { "root_cause": string, // Identified root cause of the error "error": { // The original error details "timestamp": string, "server_name": string, "tool_name": string, "message": string, "stack_trace": string // Only if include_stack_trace is true }, "suggested_actions": string[], // List of actionable steps to resolve "related_errors": [ // Similar errors for pattern analysis { "timestamp": string, "message": string } ] }
Examples:
Permission error -> { server_name: "slack-mcp-server", error_message: "permission denied" }
Rate limit debugging -> { server_name: "github_mcp", error_message: "rate limit", include_stack_trace: true }
Recurring error -> { server_name: "jira-mcp-server", error_message: "timeout" }
Error Handling:
Returns error if server_name not found
Returns "Error not found" if no matching error in logs
Provides best-effort analysis even for unknown error patterns
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server_name | Yes | Name of the MCP server where the error occurred | |
| error_message | Yes | The error message or pattern to search for | |
| response_format | No | Output format: 'markdown' for human-readable or 'json' for machine-readable | markdown |
| include_stack_trace | No | Whether to include full stack traces in the response (default: false) |