MCP DuckDuckGo Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| duckduckgo_searchC | Search DuckDuckGo Instant Answer API for a query string |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility for confusion or overlap. The single tool is clearly distinct by default.
The naming is perfectly consistent as there is only one tool. The verb_noun pattern is clear and appropriate.
A single tool for a search service is minimal. It may be sufficient for simple queries, but the tool count feels thin for a typical API surface.
The tool only performs a simple search. There are no supporting tools for pagination, fetching detailed results, or handling errors, making the surface incomplete for advanced use cases.