Skip to main content
Glama
deepseek-search

deepseek-search

by BryleXia

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEEPSEEK_API_KEYYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • Query is limited to 128 Unicode characters; longer queries are truncated with a warning.

  • site:example.com, -site:example.com, -word, "exact phrase", -"phrase", lang:zh,en, after:YYYY-MM-DD, before:YYYY-MM-DD.

Guidance:

  • Best for Chinese-language and China-focused queries; pair it with another provider for English technical documentation.

  • need_content=false by default; use deepseek_fetch on selected URLs when full page text is needed.

  • Empty results are a normal successful search, not an error.

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.

  • Not a crawler: for whole-site crawl/map or JS-heavy pages, use a dedicated crawler.

  • Localhost/private/internal addresses and URLs with credentials are rejected.

  • Content is truncated at max_chars.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessOutdated data