EZ Web Search MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Performs a web search using DuckDuckGo and returns a list of 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 1 tool
With only a single tool, there is no possibility of ambiguity or overlap. The tool's purpose is clearly defined as performing a web search.
The tool name 'search' is a clear verb and, being the only tool, there is no inconsistency in naming patterns.
The server has only one tool, which is on the thin side. However, for a focused web search server, a single tool can be sufficient, but it still falls into the borderline category of 1-2 tools.
The domain is web search, and the single tool directly fulfills that purpose without obvious gaps. It performs a search and returns results, which covers the core functionality.