Skip to main content
Glama
taylorleese

mcp-toolz

ask_deepseek

Get AI-powered answers or second opinions on specific context entries using DeepSeek's analysis capabilities.

Instructions

Ask DeepSeek a question about a context entry, or get a general second opinion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_idYesContext ID to ask about
questionNoOptional specific question to ask about the context. If not provided, gets a general second opinion.

Implementation Reference

  • MCP tool handler for 'ask_deepseek': fetches context, calls DeepSeekClient.get_second_opinion, saves response if generic opinion, returns formatted result or error.
    if name == "ask_deepseek":
        context_id = arguments["context_id"]
        question = arguments.get("question")
        context = self.storage.get_context(context_id)
        if not context:
            return [TextContent(type="text", text=f"Context {context_id} not found")]
    
        try:
            deepseek_client = DeepSeekClient()
            response = deepseek_client.get_second_opinion(context, question)
    
            # Only save to database if it's a generic second opinion (no custom question)
            if not question:
                self.storage.update_deepseek_response(context_id, response)
    
            header = "DeepSeek's Answer:" if question else "DeepSeek's Opinion:"
            return [TextContent(type="text", text=f"{header}\n\n{response}")]
        except ValueError as e:
            return [TextContent(type="text", text=f"Error: {e}")]
  • Input schema for the 'ask_deepseek' tool: requires 'context_id', optional 'question' for specific query or general second opinion.
    Tool(
        name="ask_deepseek",
        description="Ask DeepSeek a question about a context entry, or get a general second opinion",
        inputSchema={
            "type": "object",
            "properties": {
                "context_id": {"type": "string", "description": "Context ID to ask about"},
                "question": {
                    "type": "string",
                    "description": (
                        "Optional specific question to ask about the context. If not provided, gets a general second opinion."
                    ),
                },
            },
            "required": ["context_id"],
        },
    ),
  • DeepSeekClient.get_second_opinion and _format_context_for_deepseek: formats context appropriately, constructs system/user prompts, calls DeepSeek API via OpenAI-compatible client to get response.
        def get_second_opinion(self, context: ContextEntry, question: str | None = None) -> str:
            """Get DeepSeek's second opinion on a context, or answer a specific question.
    
            Args:
                context: The context entry to analyze
                question: Optional specific question to ask. If None, provides general second opinion.
            """
            if question:
                # Custom question mode
                system_prompt = """You are a senior software engineering consultant answering questions about code, \
    architecture decisions, and implementation plans.
    
    Provide clear, actionable answers based on the context provided."""
                user_content = self._format_context_for_deepseek(context, question)
            else:
                # Generic second opinion mode
                system_prompt = """You are a senior software engineering consultant providing second opinions on code, \
    architecture decisions, and implementation plans.
    
    Your role is to:
    - Provide constructive, balanced feedback
    - Highlight both strengths and potential issues
    - Suggest alternatives when appropriate
    - Point out edge cases or security concerns
    - Be concise but thorough
    
    Format your response clearly with sections as needed."""
                user_content = self._format_context_for_deepseek(context)
    
            response = self.client.chat.completions.create(
                model=self.model,
                messages=[
                    {"role": "system", "content": system_prompt},
                    {"role": "user", "content": user_content},
                ],
            )
    
            return response.choices[0].message.content or ""
    
        def _format_context_for_deepseek(self, context: ContextEntry, question: str | None = None) -> str:
            """Format a context entry for DeepSeek consumption.
    
            Args:
                context: The context entry to format
                question: Optional specific question to append
            """
            parts = [
                f"# Context: {context.title}",
                f"\n**Type:** {context.type}",
                f"**Timestamp:** {context.timestamp.isoformat()}",
            ]
    
            if context.tags:
                parts.append(f"**Tags:** {', '.join(context.tags)}")
    
            parts.append("\n## Content\n")
    
            # Add specific content based on type
            if context.content.messages:
                parts.append("### Conversation\n")
                for msg in context.content.messages:
                    parts.append(msg)
    
            if context.content.code:
                parts.append("### Code\n")
                for file_path, code in context.content.code.items():
                    parts.append(f"**File:** `{file_path}`\n```\n{code}\n```\n")
    
            if context.content.suggestions:
                parts.append(f"### Suggestion\n{context.content.suggestions}\n")
    
            if context.content.errors:
                parts.append(f"### Error/Debug Info\n```\n{context.content.errors}\n```\n")
    
            # Add question or default request
            if question:
                parts.append(f"\n---\n**Question:** {question}")
            else:
                parts.append("\n---\nPlease provide a second opinion on the above context.")
    
            return "\n".join(parts)
  • Registration of the list_tools method on the MCP Server instance, which includes the 'ask_deepseek' tool in its returned list.
    self.server.call_tool()(self.call_tool)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the tool can 'ask a question' or 'get a general second opinion,' but lacks details on behavioral traits such as response format, rate limits, authentication needs, or whether it's read-only or mutative. This is a significant gap for an AI query tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. It uses clear language with zero waste, making it easy to understand quickly without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (querying an AI model) and lack of annotations and output schema, the description is incomplete. It doesn't explain what the response looks like, potential limitations, or how it integrates with other tools like context_get. For a tool with no structured behavioral data, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters (context_id and question). The description adds minimal value beyond the schema by implying that 'question' is optional and if omitted, it defaults to a 'general second opinion.' This aligns with the schema but doesn't provide additional syntax or format details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Ask DeepSeek a question about a context entry, or get a general second opinion.' It specifies the verb ('ask') and resource ('DeepSeek'), though it doesn't explicitly differentiate from sibling tools like ask_chatgpt, ask_claude, or ask_gemini beyond naming the specific AI model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning 'about a context entry' and 'general second opinion,' suggesting it's for querying AI models. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like ask_chatgpt or context_search, nor does it specify prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorleese/mcp-toolz'

If you have feedback or need assistance with the MCP directory API, please join our Discord server