ds-web-mcp

DeepSeek web search

web_search

Read-only

Research current events, prices, releases, and up-to-date sources by asking DeepSeek with live web search enabled; returns the answer plus a session link.

Instructions

Ask DeepSeek with its web search turned on. Use for current events, prices, releases, or anything requiring up-to-date sources. Returns the answer plus the session link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "web_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The question to research on the live web.
`thinking`	No	Enable DeepSeek reasoning mode. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 30, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety/external-call profile is covered. The description adds value beyond that by disclosing the return shape (answer plus session link), which matters because there is no output schema. It does not mention latency, cost, or how sessions are created/managed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action, then usage triggers, then return value. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only search tool with no output schema, the description covers purpose, triggers, and return content. Minor gaps remain around session handling and the effect of the `thinking` flag, but nothing prevents correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both `query` and `thinking` are already documented, and the description adds no extra meaning about the reasoning toggle or query formatting. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action and mechanism: ask DeepSeek with web search enabled, returning an answer plus a session link. It implicitly separates itself from the plain `chat` sibling by emphasizing live-web grounding, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases (current events, prices, releases, anything requiring up-to-date sources), which is a clear trigger condition. It stops short of stating when NOT to use it or pointing at `chat` for non-web questions, so there is no explicit alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server