open-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 |
|---|---|
| searchA | Search the web via DuckDuckGo. No API key needed. Use advanced query techniques for best results:
Args: query: Search query (use operators for precision) max_results: Number of results (1-25, default 10) region: Region code (wt-wt=global, us-en, uk-en, etc.) time_range: d=past day, w=past week, m=past month, y=past year site: Limit to domain (e.g. "github.com", "stackoverflow.com") |
| fetchB | Fetch a URL and extract readable content (HTML → clean text). Args: url: The URL to fetch max_chars: Max characters to return (default 20000, truncates if exceeded) |
| researchA | Combined search + fetch: searches, then fetches the top N result pages. Returns search results with full extracted content for the top hits. Use advanced query techniques — don't just pass raw user questions. Reformulate into precise search operators. Args: query: Search query (use operators for precision) max_results: Total search results to return (default 5) fetch_top: How many top results to auto-fetch content from (default 3) max_chars_per_page: Max chars per fetched page (default 10000) region: Region code time_range: d=day, w=week, m=month, y=year site: Limit to domain |
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 3 tools
fetch, search, and research target distinct inputs (URL vs query vs combined workflow), but research is a composite of search+fetch and could be over-selected when simpler tools suffice. Descriptions clarify the boundaries well, so misselection risk is minor.
All three tool names are single lowercase verbs (fetch, search, research), forming a consistent action-oriented pattern with no deviations. This makes the set predictable and easy to scan.
Three tools is lean but perfectly scoped for a web search and content extraction server. Each tool earns its place: one for URL fetching, one for search queries, and one for combined research.
Core operations (search, fetch, combined research) are well covered, with no dead ends for typical workflows. Minor gaps include no batch fetch for a list of known URLs and no pagination beyond max_results for deeper search.