deepseek-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key, used by the server to authenticate requests. |
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 |
|---|---|
| deepseek_searchA | Search the live web with DeepSeek's search engine. Returns ranked results with title, URL, snippet, long summary, publish date, site name, authority (0-4; >=3 highly authoritative), and relevance score (0-3; >=1.5 high quality). Query limits and operators:
Guidance:
|
| deepseek_fetchA | Fetch a single public HTTP/HTTPS page with DeepSeek and return its title and Markdown content. Use for a specific URL when search summaries are insufficient.
|
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
The two tools have crisply distinct roles: one searches for ranked results by query, the other retrieves full Markdown content for a single URL. The search description explicitly points to the fetch tool when summaries are insufficient, so an agent will never misselect between them.
Both names follow the same deepseek_<verb> pattern (deepseek_search, deepseek_fetch), using consistent snake_case with an unambiguous action verb. Zero variation in convention across the set.
Two tools is slightly under the typical 3-15 band, but search+fetch is the canonical minimal-yet-complete pair for a web retrieval server, and each tool clearly earns its place. Nothing feels padded or missing at the count level.
Query-based search and single-URL fetching together cover the core retrieve-and-read lifecycle for this domain, and out-of-scope operations (whole-site crawl/map, JS-heavy rendering) are explicitly delegated to dedicated crawlers rather than left as silent gaps. Minor gap: no pagination or multi-URL batch fetch, though agents can loop over fetch calls.