my-pal-mcp-server/docs/tools/thinkdeep.md

ThinkDeep Tool - Extended Reasoning Partner

Get a second opinion to augment Claude's own extended thinking

The thinkdeep tool provides extended reasoning capabilities, offering a second perspective to augment Claude's analysis. It's designed to challenge assumptions, find edge cases, and provide alternative approaches to complex problems.

Thinking Mode

Default is high (16,384 tokens) for deep analysis. Claude will automatically choose the best mode based on complexity - use low for quick validations, medium for standard problems, high for complex issues (default), or max for extremely complex challenges requiring deepest analysis.

Example Prompt

Think deeper about my authentication design with pro using max thinking mode and brainstorm to come up 
with the best architecture for my project

Key Features

• Uses Gemini's specialized thinking models for enhanced reasoning capabilities
• Provides a second opinion on Claude's analysis
• Challenges assumptions and identifies edge cases Claude might miss
• Offers alternative perspectives and approaches
• Validates architectural decisions and design patterns
• File reference support: "Use gemini to think deeper about my API design with reference to api/routes.py"
• Image support: Analyze architectural diagrams, flowcharts, design mockups: "Think deeper about this system architecture diagram with gemini pro using max thinking mode"
• Enhanced Critical Evaluation (v2.10.0): After Gemini's analysis, Claude is prompted to critically evaluate the suggestions, consider context and constraints, identify risks, and synthesize a final recommendation - ensuring a balanced, well-considered solution
• Web search capability: When enabled (default: true), identifies areas where current documentation or community solutions would strengthen the analysis and suggests specific searches for Claude

Tool Parameters

• prompt: Your current thinking/analysis to extend and validate (required)
• model: auto|pro|flash|o3|o3-mini|o4-mini|gpt4.1 (default: server default)
• problem_context: Additional context about the problem or goal
• focus_areas: Specific aspects to focus on (architecture, performance, security, etc.)
• files: Optional file paths or directories for additional context (absolute paths)
• images: Optional images for visual analysis (absolute paths)
• temperature: Temperature for creative thinking (0-1, default 0.7)
• thinking_mode: minimal|low|medium|high|max (default: high, Gemini only)
• use_websearch: Enable web search for documentation and insights (default: true)
• continuation_id: Continue previous conversations

Usage Examples

Architecture Design:

"Think deeper about my microservices authentication strategy with pro using max thinking mode"

With File Context:

"Use gemini to think deeper about my API design with reference to api/routes.py and models/user.py"

Visual Analysis:

"Think deeper about this system architecture diagram with gemini pro - identify potential bottlenecks"

Problem Solving:

"I'm considering using GraphQL vs REST for my API. Think deeper about the trade-offs with o3 using high thinking mode"

Code Review Enhancement:

"Think deeper about the security implications of this authentication code with pro"

Best Practices

• Provide detailed context: Share your current thinking, constraints, and objectives
• Be specific about focus areas: Mention what aspects need deeper analysis
• Include relevant files: Reference code, documentation, or configuration files
• Use appropriate thinking modes: Higher modes for complex problems, lower for quick validations
• Leverage visual context: Include diagrams or mockups for architectural discussions
• Build on discussions: Use continuation to extend previous analyses

Enhanced Critical Evaluation Process

The thinkdeep tool includes a unique two-stage process:

1. Gemini's Analysis: Extended reasoning with specialized thinking capabilities
2. Claude's Critical Evaluation: Claude reviews Gemini's suggestions, considers:
   • Context and constraints of your specific situation
   • Potential risks and implementation challenges
   • Trade-offs and alternatives
   • Final synthesized recommendation

This ensures you get both deep reasoning and practical, context-aware advice.

When to Use ThinkDeep vs Other Tools

• Use thinkdeep for: Extending specific analysis, challenging assumptions, architectural decisions
• Use chat for: Open-ended brainstorming and general discussions
• Use analyze for: Understanding existing code without extending analysis
• Use codereview for: Finding specific bugs and security issues