F
license-
qualityD
maintenanceEnables web search capabilities using DuckDuckGo's free API without requiring authentication or API keys.
duckduckgo
by com.jojapi
Server Details
DuckDuckGo: The DuckDuckGo Search API is a tool that allows developers and businesses to integrate.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
C2.2/5.0
Tool DescriptionsD
Average 1.9/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only a single tool, there is no possibility of confusing it with another tool. The tool's purpose is somewhat vague, but the dimension concerns inter-tool ambiguity.
Naming Consistency4/5
The single tool name 'get' is a simple verb, and with no other tools there is no pattern to violate. However, the name is generic and does not convey the domain.
Tool Count2/5
A single tool is insufficient for a search server, which typically requires multiple operations such as searching, fetching results, and handling pagination. The calibration indicates one tool is too few for the apparent scope.
Completeness1/5
The server provides only a generic 'get' tool with no clear search parameters or result handling. There are no operations for different search types, pagination, or filtering, making the surface severely incomplete.
Available Tools
1 toolgetSearchDInspect
DuckDuckGo Search Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | You can use DuckDuckGo search parameters. |
Tool Definition Quality
D1.9/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only mentions billing, not behavioral traits like rate limits, result format, security, or side effects. Given that this is a search tool, it likely reads data, but that is not disclosed. The description doesn't explain what happens when calling it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is incredibly short, almost under-specified. It contains one sentence about billing. While conciseness is valued, this is not appropriately sized: it lacks necessary detail. It does get straight to the point, but at the cost of clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a search tool with an output schema not provided, and it is likely to return web results, but the description omits this. There is no mention of output, error conditions, or usage context. With one parameter and no annotations, the description is inadequate.
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% because the only parameter 'q' has a description saying 'You can use DuckDuckGo search parameters.' This is vague but does provide some meaning beyond the parameter name. The description's only additional info is the billing note, which doesn't clarify parameter usage. Baseline is 3 due to full coverage, but the param description is unhelpful.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description is extremely vague: 'DuckDuckGo Search Billing per call: 1 Credits.' It mentions billing but does not state what the tool does (e.g., 'Search the web using DuckDuckGo'). The title 'Search' is barely more specific. It fails to distinguish from any potential sibling tools and doesn't convey the action or resource.
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?
No guidance on when to use this tool. It doesn't mention scenarios, alternatives, or exclusions. The only additional info is a billing note, which might imply cost considerations but doesn't provide context on use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceDuckDuckGo Search MCP Server. Scrapes DuckDuckGo Lite directly — no API key required, no rate limits, robust anti-bot protection.3MIT
- Alicense-qualityFmaintenanceEnables AI agents to search the web, find news, and read page content via DuckDuckGo without an API key.2MIT
- Alicense-qualityDmaintenanceA free and unlimited web search server that enables AI models to search, crawl, and research web content using DuckDuckGo without requiring API keys. It features parallel crawling and a smart ranking system to prioritize the most relevant information for complex queries.2164MIT