web-search-mcp
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web and return titles, URLs, and text snippets for matching pages. Uses DuckDuckGo as the search backend — no API key required. Results are suitable for driving follow-up fetches with WebFetch. Args: params (WebSearchInput): Validated search parameters containing: - query (str): Search query, 1–500 characters, must not be whitespace-only. - max_results (int): Maximum results to return, 1–20 (default: 5). - region (str | None): Locale code such as "us-en" or "br-pt". When omitted the backend's worldwide default ("wt-wt") is used. Returns: str: JSON-formatted string on success: Examples: - "Python asyncio tutorial" -> returns up to 5 results about asyncio - query="news", region="br-pt" -> returns Brazilian Portuguese news results - query=" " -> rejected by input validation before any search is performed Error cases: - Whitespace-only or empty query: rejected by Pydantic validation - max_results outside 1–20: rejected by Pydantic validation - Backend failure (network error, rate limit, DuckDuckGo unavailable): returns "Error: Search failed: " |
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
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly defined and distinct from any other potential tool.
The single tool name 'web_search' follows a clear verb_noun pattern, which is consistent and predictable. Even with only one tool, the naming is appropriate and self-explanatory.
The server is a focused web search utility with a single tool that fully encapsulates its intended functionality. Despite having fewer tools than typical MCP servers, the scope is appropriately narrow and well-defined.
The web_search tool covers the entire search workflow, including query validation, result limiting, and region specification. No additional search-related operations are needed for the stated purpose.