search-rotation
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 |
|---|---|
| web_searchA | Web search with automatic round-robin across multiple free search APIs (Tavily, Firecrawl, Parallel, Exa, Google PSE, DuckDuckGo) including transparent failover. Returns numbered results with title, URL, snippet and publication date when available. Time filters restrict rotation and failover to compatible providers; never silently dropped. |
| fetch_urlA | Fetch a web page and return its content as markdown. Rotates across extraction providers (Jina Reader, Firecrawl, Parallel, Tavily, Exa) with failover. |
| engine_statusA | Read engine configuration, per-capability authentication requirements, local usage and quota sources. This is not a live health check. Historical errors do not prove a current failure; disabled engines are not necessarily missing credentials. |
| open_dashboardA | Open the local dashboard (API keys, engine order and toggles, quota view) in a web browser. Use when the user wants to configure engines or check quota. |
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 4 tools
web_search and fetch_url are clearly distinct (search results vs. page content). engine_status and open_dashboard both relate to configuration/quota, but one is a read-only config query and the other opens a browser UI, so some care is needed but descriptions mitigate ambiguity.
Names are all lowercase snake_case, but styles are mixed: fetch_url and open_dashboard follow verb_noun, while web_search and engine_status are noun-style phrases. The pattern is readable but not fully consistent.
Four tools is well-scoped for a search-rotation server: search, fetch, engine status, and dashboard access each cover a distinct need without bloat.
The core lifecycle of searching, fetching, inspecting engine status, and opening configuration UI is covered. A minor gap is the lack of programmatic engine configuration, but the dashboard tool reasonably covers that user-driven workflow.