Skip to main content
Glama
hbhszy

web-search-mcp

by hbhszy

web_search

Search the web and get up-to-date answers through DeepSeek's search-enabled dialogue. Optionally enable reasoning mode for detailed analysis.

Instructions

Search the web using DeepSeek's search-enabled chat. Returns a search-grounded response with up-to-date information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query
thinkingNoEnable DeepSeek thinking/reasoning mode. When true, the model will reason through the query before answering, and the reasoning trace is included in the response. (default: false)
modelNoDeepSeek model mode (default: from server config)
Behavior3/5

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

The description states that the tool returns a 'search-grounded response with up-to-date information', which implies read-only behavior, but it does not explicitly disclose side effects, authentication needs, or limitations. Without annotations, the description carries a heavier burden and falls short of full transparency.

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

Conciseness4/5

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

The description is a single sentence that conveys the essential function without unnecessary words. While it is concise, it could be slightly expanded to improve clarity without becoming verbose.

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

Completeness3/5

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

Given that there is no output schema, the description should elaborate on the return format. It mentions 'search-grounded response' but does not specify structure or content. The lack of sibling tools reduces the need for differentiation, but completeness is only moderate.

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?

The input schema has 100% description coverage for all three parameters, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides for the parameters.

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

Purpose5/5

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

The description uses a specific verb 'Search' and clearly identifies the resource 'the web using DeepSeek's search-enabled chat', leaving no ambiguity about what the tool does.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus any alternatives, nor are there any conditions or prerequisites mentioned. The description lacks context for appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hbhszy/web-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server