DeepSeek MCP Server

list_conversations

Read-onlyIdempotent

Retrieve all stored conversation IDs from memory to debug persistence behavior without making API calls.

Instructions

List all conversation IDs currently stored in this MCP process memory. This tool takes no parameters and does not call the DeepSeek API. Useful for debugging conversation persistence behavior.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`status`	No
`message`	No
`retryable`	No
`error_type`	No
`suggestion`	No
`conversation_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Sep 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "conversation_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "error_type": {
+      "enum": [
+        "deepseek_api_error",
+        "tool_execution_error"
+      ],
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "suggestion": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Addedv0.5.0May 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral facts beyond that: it takes no parameters and, notably, does not call the DeepSeek API, meaning it reads local process state rather than network data. Return format is covered by the existing output schema.

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 and scope, followed by the no-param/no-API constraint and then the use case. No filler, every sentence carries distinct information.

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

Completeness5/5

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

For a zero-parameter, read-only inspection tool with a full annotation set and an output schema, the description supplies everything needed: what is listed, where it comes from, that no API call occurs, and why one would use it.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. The description reinforces this by explicitly stating 'takes no parameters', which prevents an agent from inventing filter arguments that appear on sibling list tools.

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?

States a specific verb (List) and resource (conversation IDs) and pins the scope precisely to 'currently stored in this MCP process memory', which separates it from the API-backed siblings like chat_completion and reset_conversation. An agent can identify what it returns without opening the schema.

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 clear usage context ('Useful for debugging conversation persistence behavior') so the agent knows when it applies, but names no alternatives or exclusions (e.g., that it only shows in-process conversations versus remote ones). Clear context without routing guidance.

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

Deploy Server