Skip to main content
Glama
deepseek-mcp-server

deepseek-mcp-server

Manage DeepSeek conversation sessions

deepseek_session

Inspect and manage persistent chat sessions: list conversations, retrieve transcripts, clear messages, delete sessions, set system prompts, or import transcripts by session ID.

Instructions

Inspect and manage the persistent conversations used by the session_id parameter on the chat tools. Actions: list every session, get one session's full transcript, clear its messages while keeping the id, delete it outright, set its standing system prompt, or import a transcript wholesale.

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": {
      "action": "<action>"
    },
    "name": "deepseek_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat to do.
systemNoThe standing system prompt, for `set_system`.
messagesNoTranscript to load, for `import`.
session_idNoRequired for every action except `list`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does usefully distinguish the non-destructive 'clear' (id preserved) from the destructive 'delete it outright'. However it leaves out whether delete is irreversible, whether these operations are scoped per-user/workspace, and whether 'import a transcript wholesale' replaces or appends to existing messages — a material ambiguity for a mutation action.

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?

Two sentences, front-loaded with the resource and purpose, followed by a compact action enumeration that maps one-to-one onto the enum values. Nothing is redundant.

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 six-action mutation tool with no annotations and no output schema, the description covers every action and clarifies that `get` returns a full transcript. The remaining gaps — import overwrite semantics, session scoping, and irreversibility of delete — are real but narrow rather than foundational.

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 schema already documents `action`, `system`, `messages`, and the `session_id` requirement. The description adds only the contextual link that `session_id` is the same identifier used by the chat tools; it adds no format, constraints, or edge-case semantics for `messages` or `system`.

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 states a specific verb pair ('inspect and manage') plus a specific resource ('persistent conversations used by the `session_id` parameter on the chat tools'), and then enumerates the six concrete operations. This cleanly separates it from siblings like deepseek_chat or deepseek_reason, which consume sessions rather than manage them.

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?

It ties the tool to the chat tools via the `session_id` parameter, which is genuine usage context, and the action list implicitly guides choice among operations (e.g. 'clear its messages while keeping the id' vs 'delete it outright'). It stops short of explicit when-not guidance or stating whether sessions should be managed before/after a chat call.

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