minimal-mcp-web-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 |
|---|---|
| web_searchA | Search the web using DuckDuckGo. Returns a list of result titles, URLs, and snippets. Use this when you need current information. |
| fetch_pageA | Fetch the text content of a web page. Returns plain text with HTML stripped. Use this to read the full content of a URL from search results. |
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 2 tools
web_search returns search results while fetch_page retrieves content from a specific URL. Their purposes are distinct and complementary, leaving no ambiguity.
Both tools use snake_case and follow a clear verb_noun pattern (web_search, fetch_page), providing predictable naming.
With 2 tools, the server is minimal but appropriately scoped for a web search service. It covers the essential search and fetch operations without unnecessary bloat.
The server covers the core workflow of searching and fetching page content. Missing advanced features like pagination or image search, but for a minimal server, it's reasonably complete.