SERPdive
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPDIVE_API_KEY | No | SERPdive API key (sd_live_...). Free at https://serpdive.com/dashboard/keys |
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 |
|---|---|
| serpdive_searchA | Search the live web and get back answer-ready page content, not a list of links. Each result carries the actual text of the page (url, title, date, content), already extracted, cleaned and trimmed for LLM use, so facts can be quoted and cited straight from the response. Use it for anything that needs current or post-training information: news, prices, releases, docs, sports, niche facts. Write the query the way a person would type it, in any language: localization is automatic. The 'mako' model (default) returns the fact-carrying sentences of each page, fast and concise, right for most questions. The 'krill' model is free and unlimited under fair use: the shortest useful answer set (~700 tokens, fewer sources, no written answer), served at low priority — right when token budget matters more than depth. The 'moby' model returns full page text: slower (~1s more) and several times more tokens, so use it only when mako's key sentences are insufficient (long-document analysis, deep research). |
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 misselection. The single search tool's purpose is clearly defined and self-contained.
The one tool name follows a clear server-prefix plus verb form and has no inconsistent conventions. There is no naming conflict or mixed pattern to confuse an agent.
The server is intentionally narrow, and the single search tool covers its core capability well. However, one tool makes the surface feel thin and leaves no supporting operations for edge cases, so it sits at the low end of acceptable.
The tool fully covers the server's stated domain of live web search with extracted, answer-ready content, including multiple output-depth modes. No obvious missing operation is needed to accomplish the server's stated purpose.