MCP Web Tools
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using DuckDuckGo. Returns a list of search results with titles, URLs, and snippets. |
| web_fetchB | Fetch the content of a web page. Returns the raw text content of the page, suitable for reading articles and documentation. |
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
The two tools have clearly distinct purposes: web_fetch retrieves the content of a specific URL, while web_search queries a search engine for results. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a consistent 'web_' prefix and snake_case naming pattern (web_fetch and web_search). This predictable structure enhances readability and usability for agents.
With only 2 tools, the server feels thin for a 'Web Tools' domain. While fetch and search are core operations, the scope suggests potential for more functionality (e.g., parsing, navigation, or analytics), making the toolset appear incomplete.
The tools cover basic web interaction (fetching content and searching), but there are notable gaps. For a web tools server, missing operations like navigating links, extracting specific data, or handling web forms limit its utility for complex agent workflows.