Skip to main content
Glama

DeepSeek Chat Completion

deepseek_chat

Chat with DeepSeek AI for general conversations. Supports multi-turn sessions, function calling, and multimodal input for flexible interaction.

Instructions

Chat with DeepSeek AI models. Supports deepseek-chat for general conversations and deepseek-reasoner for complex reasoning tasks with chain-of-thought explanations. Features: multi-turn sessions (session_id), function calling (tools parameter), thinking mode, JSON output mode, multimodal input (when enabled), automatic cost tracking, and model fallback with circuit breaker resilience.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messagesYesArray of conversation messages. Each message has role (system/user/assistant/tool) and content (string or array of content parts for multimodal). Tool messages require tool_call_id.
modelNoModel to use. Both run DeepSeek V3.2 (128K context). deepseek-chat: non-thinking mode (max 8K output), deepseek-reasoner: thinking mode (max 64K output)deepseek-chat
temperatureNoSampling temperature (0-2). Higher = more random. Default: 1.0. Ignored when thinking mode is enabled.
max_tokensNoMaximum tokens to generate. deepseek-chat: max 8192, deepseek-reasoner: max 65536
streamNoEnable streaming mode. Returns full response after streaming completes.
toolsNoArray of tool definitions for function calling. Each tool has type "function" and a function object with name, description, and parameters (JSON Schema).
tool_choiceNoControls which tool the model calls. "auto" (default), "none", "required", or {type:"function",function:{name:"..."}}
thinkingNoEnable thinking mode. When enabled, temperature/top_p/frequency_penalty/presence_penalty are automatically ignored. Use {type: "enabled"} to activate.
json_modeNoEnable JSON output mode. The model will output valid JSON. Include the word "json" in your prompt for best results. Supported by both models.
session_idNoSession ID for multi-turn conversations. When provided, previous messages from this session are prepended to the current messages. If the session does not exist, it is created automatically. Omit for stateless single-turn requests.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
reasoning_contentNo
modelYes
usageYes
finish_reasonYes
tool_callsNo
session_idNo
Behavior3/5

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

With no annotations, the description carries full burden. It mentions features like cost tracking and circuit breaker resilience but does not explain behaviors such as rate limits, error handling, or how to enable multimodal input. Some transparency is provided for model selection and thinking mode, but gaps remain.

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 concise (three sentences) with a front-loaded purpose statement. It efficiently lists key features, though the bullet-like format within a paragraph could be more structured. Overall, it earns its keep without excessive verbosity.

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?

Given the tool's complexity (10 parameters, rich schema, output schema exists), the description covers the main purpose and features. It does not discuss error handling or edge cases, but the presence of an output schema reduces the need to describe return values. Adequate for an AI agent.

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 baseline is 3. The description lists features but does not add meaning beyond the schema's parameter descriptions. No new context is provided about parameters.

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?

The description clearly states it is for chatting with DeepSeek AI models and distinguishes between deepseek-chat for general conversations and deepseek-reasoner for complex reasoning. However, it does not explicitly differentiate from the sibling tool deepseek_sessions, though the intent is implied.

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

Usage Guidelines3/5

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

The description provides some usage guidance by explaining which model to use for general vs. reasoning tasks. However, it lacks explicit when-to-use vs. when-not-to-use guidance, nor does it mention prerequisites or alternative tools. The guidance is implied but not comprehensive.

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

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