Skip to main content
Glama
booleamu

DeepSeek MCP Server

by booleamu

deepseek_multi_turn

Carry on multi-turn conversations with DeepSeek by sending full message history. Use a session key to resume previous dialogues.

Instructions

多轮对话,携带完整历史消息上下文调用 DeepSeek 模型。支持通过 session_key 续接上一次对话

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNo模型名称,默认 deepseek-chat
messagesYes对话历史消息数组,每条消息包含 role 和 content
max_tokensNo最大输出 token 数,默认 4096
session_keyNo会话标识,用于续接上一次对话。首次对话不传,从返回结果中获取 session_key 后传入即可续接
temperatureNo采样温度,默认 1.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that the tool carries full message history and supports session continuation, but it does not explain underlying mechanics (e.g., whether full history is always required, session expiration) or mention side effects/return format. Some value is added despite gaps.

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?

A single, concise Chinese sentence with zero filler. It front-loads the core purpose (multi-turn dialogue with full context) and then adds the unique session_key feature. Every word earns its place.

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?

The description covers the tool's purpose and key feature, and the schema covers all 5 parameters, so it is adequate. However, it lacks details about return values (no output schema), error handling, or explicit comparison to alternatives, leaving some context unexplained for a 5-parameter tool.

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 the baseline is 3. The description mentions session_key ('支持通过 session_key 续接上一次对话') but adds no additional parameter semantics beyond what the schema already documents for each field.

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 explicitly states the verb+resource: '多轮对话,携带完整历史消息上下文调用 DeepSeek 模型' (multi-turn dialogue calling DeepSeek model with full history). It also highlights the distinguishing session_key continuation feature, which sets it apart from sibling tools like deepseek_chat and deepseek_reasoner.

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?

The description clearly implies usage for multi-turn conversations: '多轮对话' and '支持通过 session_key 续接上一次对话' (supports resuming via session_key). However, it does not explicitly name alternatives or state when not to use the tool, though sibling names provide context.

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/booleamu/deepseek-mcp-server'

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