Skip to main content
Glama
misanthropic-ai

DuckDuckGo MCP Server

ddg-ai-chat

Query DuckDuckGo's AI models to get answers, explanations, or assistance with questions using various language models.

Instructions

Chat with DuckDuckGo AI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYesMessage or question to send to the AI
modelNoAI model to usegpt-4o-mini

Implementation Reference

  • Handler for 'ddg-ai-chat' tool: extracts keywords and model from arguments, calls DDGS().chat(), and returns the response as TextContent.
    elif name == "ddg-ai-chat":
        keywords = arguments.get("keywords")
        if not keywords:
            raise ValueError("Missing keywords")
        
        model = arguments.get("model", "gpt-4o-mini")
        
        # Perform AI chat
        ddgs = DDGS()
        result = ddgs.chat(
            keywords=keywords,
            model=model
        )
        
        return [
            types.TextContent(
                type="text",
                text=f"DuckDuckGo AI ({model}) response:\n\n{result}",
            )
        ]
  • JSON Schema for input validation of 'ddg-ai-chat' tool: requires 'keywords', optional 'model' with specific enums.
    inputSchema={
        "type": "object",
        "properties": {
            "keywords": {"type": "string", "description": "Message or question to send to the AI"},
            "model": {"type": "string", "enum": ["gpt-4o-mini", "llama-3.3-70b", "claude-3-haiku", "o3-mini", "mistral-small-3"], "description": "AI model to use", "default": "gpt-4o-mini"},
        },
        "required": ["keywords"],
    },
  • Registration of the 'ddg-ai-chat' tool in the @server.list_tools() handler, defining name, description, and schema.
    types.Tool(
        name="ddg-ai-chat",
        description="Chat with DuckDuckGo AI",
        inputSchema={
            "type": "object",
            "properties": {
                "keywords": {"type": "string", "description": "Message or question to send to the AI"},
                "model": {"type": "string", "enum": ["gpt-4o-mini", "llama-3.3-70b", "claude-3-haiku", "o3-mini", "mistral-small-3"], "description": "AI model to use", "default": "gpt-4o-mini"},
            },
            "required": ["keywords"],
        },
    ),
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers almost none. 'Chat with DuckDuckGo AI' doesn't reveal whether this is a read-only operation, if it requires authentication, what rate limits apply, whether conversations are persistent, or what the typical response format looks like. For a chat tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core functionality ('Chat with DuckDuckGo AI') and every word earns its place. This is a model of efficiency in tool description writing.

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 that this is a chat tool with no annotations, no output schema, and 2 parameters, the description is insufficiently complete. It doesn't explain what kind of responses to expect, whether there are conversation contexts, what the AI's capabilities or limitations are, or any behavioral characteristics. For a tool that presumably involves AI interaction, more context about the nature of the chat would be expected.

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?

The schema description coverage is 100%, so both parameters are well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema (keywords for the message, model selection from specific AI models). This meets the baseline expectation when the schema does the heavy lifting, but doesn't provide extra context about parameter usage or constraints.

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 'Chat with DuckDuckGo AI' clearly states the verb ('Chat') and resource ('DuckDuckGo AI'), making the purpose immediately understandable. It distinguishes this tool from its siblings (image-search, news-search, text-search, video-search) by specifying it's for AI chat rather than search operations. However, it doesn't specify what kind of chat (e.g., conversational, Q&A) or the scope of the AI's capabilities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its sibling tools. It doesn't mention that this is for AI-powered conversations rather than traditional search operations, nor does it suggest alternatives like using text-search for factual queries. There's no context about appropriate use cases or limitations.

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/misanthropic-ai/ddg-mcp'

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