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
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clear and distinct by definition.
A single tool named web_search follows a clear verb_noun convention. Consistency is trivially maintained since there are no other tools to conflict.
One tool for a web search server is borderline. While it serves a specific purpose, the lack of any auxiliary tools (e.g., for history, preferences, or pagination) makes the server feel minimal, though not unreasonable for a focused search utility.
The tool covers the core search workflow effectively, returning titles, URLs, and snippets. However, it lacks advanced search options (filters, pagination, explicit backend selection) that could round out the surface, though these are not strictly required for basic search.