websearch-ring
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | No | Optional Exa API key; empty uses keyless mode | |
| WEBSEARCH_UA | No | User-Agent used for Bing scraping | Chrome UA |
| TAVILY_API_KEY | No | Optional Tavily API key; empty uses keyless mode | |
| WEBSEARCH_TTL_MS | No | Cache TTL in milliseconds; 0 disables cache | 1200000 |
| WEBSEARCH_VENDORS | No | Vendor rotation order, comma-separated | exa,tavily,bing |
| WEBSEARCH_MAX_CHARS | No | Maximum characters of returned text | 12000 |
| WEBSEARCH_TIMEOUT_MS | No | Timeout for each vendor in milliseconds | 12000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web. Rotates across multiple keyless search backends with automatic failover, so it stays available regardless of which chat model or provider the client uses. Returns titles, URLs and snippets, and reports which backend served the result. |
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
There is only one tool, so there is no possibility of confusion with another tool on the server. Its purpose is clearly stated as web search with automatic backend failover.
The single tool follows a clear, conventional snake_case verb_noun pattern (web_search). With only one tool, consistency is trivially satisfied.
A single tool is thin, but the server's stated purpose—reliable web search across keyless backends—is genuinely narrow, making one tool defensible. Still, it sits at the low end of the appropriate range.
The tool returns titles, URLs and snippets, which covers basic search, but offers no pagination, filtering, or fetch/content-retrieval options. Agents needing page content or advanced query controls would hit a dead end.