Skip to main content
Glama
OEvortex

DuckDuckGo Search MCP

by OEvortex
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Web Search

web-search
Read-only

Retrieve web search results from DuckDuckGo and AI-generated answers. Switch between standard results and AI responses with customizable backends.

Instructions

Search the web. Use mode="web" for standard DuckDuckGo results (titles, URLs, snippets). Use mode="ai" for AI-generated answers — pick backend="iask" (default) or backend="monica".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoSearch mode. "web" returns DuckDuckGo search results. "ai" returns an AI-generated answer.web
queryYesThe search query or question.
backendNoAI backend when mode="ai": "iask" or "monica". Ignored in web mode.iask
iaskModeNoIAsk mode when backend="iask": "question", "academic", "forums", "wiki", or "thinking". Default: "thinking".thinking
numResultsNoNumber of web results (1-20). Web mode only. Default: 3.
detailLevelNoIAsk detail level when backend="iask": "concise", "detailed", or "comprehensive".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv1.4.0
    • addedInput schema / properties / backend
      Added value: +{
+  "default": "iask",
+  "description": "AI backend when mode=\"ai\": \"iask\" or \"monica\". Ignored in web mode.",
+  "enum": [
+    "iask",
+    "monica"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / detailLevel
      Added value: +{
+  "description": "IAsk detail level when backend=\"iask\": \"concise\", \"detailed\", or \"comprehensive\".",
+  "enum": [
+    "concise",
+    "detailed",
+    "comprehensive"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / iaskMode
      Added value: +{
+  "default": "thinking",
+  "description": "IAsk mode when backend=\"iask\": \"question\", \"academic\", \"forums\", \"wiki\", or \"thinking\". Default: \"thinking\".",
+  "enum": [
+    "question",
+    "academic",
+    "forums",
+    "wiki",
+    "thinking"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / mode / default
      Previous value: -"short"New value: +"web"
    • changedInput schema / properties / mode / description
      Previous value: -"Choose 'short' for basic results (no Description) or 'detailed' for full results (includes Description)."New value: +"Search mode. \"web\" returns DuckDuckGo search results. \"ai\" returns an AI-generated answer."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "short",
-  "detailed"
-]New value: +[
+  "web",
+  "ai"
+]
    • changedInput schema / properties / numResults / description
      Previous value: -"Specify how many results to display (default: 3, maximum: 20)."New value: +"Number of web results (1-20). Web mode only. Default: 3."
    • changedInput schema / properties / query / description
      Previous value: -"Enter your search query to find the most relevant web pages."New value: +"The search query or question."
  2. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "short",
+  "description": "Choose 'short' for basic results (no Description) or 'detailed' for full results (includes Description).",
+  "enum": [
+    "short",
+    "detailed"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / numResults / default
      Previous value: -10New value: +3
    • changedInput schema / properties / numResults / description
      Previous value: -"Number of results to return (default: 10)"New value: +"Specify how many results to display (default: 3, maximum: 20)."
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "description": "Page number (default: 1)",
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / query / description
      Previous value: -"The search query"New value: +"Enter your search query to find the most relevant web pages."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the tool is inherently read-only. The description adds behavioral context: what each mode returns (titles/URLs/snippets vs. AI answer), default backends, and that mode can be chosen. No contradictions; description supplements annotations well.

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—two short sentences. It is front-loaded with the primary action and uses line breaks for readability. Every phrase adds value; no wasted words.

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

Completeness4/5

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

Given no output schema, the description adequately covers return types per mode. It mentions key parameters (mode, backend) but omits mentioning 'numResults' for web mode or 'iaskMode'/'detailLevel' for AI mode. However, since the schema provides full descriptions and the tool is simple, completeness is high but not perfect.

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 coverage is 100%, so baseline is 3. The description adds minimal parameter semantics beyond the schema, only noting the default value for 'backend'. It does not elaborate on 'numResults', 'iaskMode', or 'detailLevel', but the schema descriptions are already sufficient. Hence score 3.

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

Purpose5/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: 'Search the web.' It distinguishes two modes with specific outputs: 'mode="web" for standard DuckDuckGo results (titles, URLs, snippets)' and 'mode="ai" for AI-generated answers'. This provides a specific verb (search) and resource (web), and differentiates the major modes effectively.

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

Usage Guidelines4/5

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

The description explicitly tells when to use each mode: 'Use mode="web" for standard DuckDuckGo results' and 'Use mode="ai" for AI-generated answers'. It also provides guidance on backend selection for AI mode. With no sibling tools, no explicit when-not is necessary, but the guidance is clear and actionable.

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/OEvortex/ddg_search'

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