multi-api-web-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MULTI_WEB_SEARCH_MODEL | No | Default search model (or 'hybrid') | gemini-3.8-flash |
| MULTI_WEB_SEARCH_API_KEY | Yes | API key | |
| MULTI_WEB_SEARCH_BASE_URL | Yes | OpenAI-compatible endpoint base URL | |
| MULTI_WEB_SEARCH_TIMEOUT_MS | No | Upstream request timeout in ms | 90000 |
| MULTI_WEB_SEARCH_FORCE_NATIVE | No | Comma-separated models forced to use Native Grounding (prevents 504 timeouts) | |
| MULTI_WEB_SEARCH_HYBRID_MODELS | No | Comma-separated models for consensus search | grok-chat-fast,gemini-3.8-flash |
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 |
|---|---|
| multi_api_web_searchB | Multi-API Web Search: Live internet search across your configured API models. Supports single model or multi-engine consensus ('hybrid'). |
| web_searchC | Multi-API Web Search: Live internet search across your configured API models. Supports single model or multi-engine consensus ('hybrid'). |
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
Both tools have the exact same description and purpose, differing only in the name prefix. An agent cannot reliably choose between them because they appear to be identical duplicates.
Both names use snake_case, but 'web_search' and 'multi_api_web_search' are near-duplicates with no clear convention. The prefixed variant is inconsistent with the generic one, making the naming feel redundant rather than patterned.
Two tools exist but they appear to serve the exact same function. One tool would be appropriate for this simple search server; the extra tool is redundant and does not earn its place.
For a web search server, the tool surface covers the core capability of performing live internet searches. No additional operations like create, update, or delete are relevant to this domain, so there are no obvious gaps.