DeepSeek MCP Server

list_models

Read-onlyIdempotent

List available DeepSeek models for selection and validation. Call this tool before passing an explicit model ID to generation tools.

Instructions

List available DeepSeek models for model selection and validation. This tool takes no parameters. Use it before passing an explicit model ID to generation tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_models"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	No
`object`	No
`status`	No
`message`	No
`retryable`	No
`error_type`	No
`suggestion`	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": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "created": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "object": {
+            "type": "string"
+          },
+          "owned_by": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "object"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error_type": {
+      "enum": [
+        "deepseek_api_error",
+        "tool_execution_error"
+      ],
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "object": {
+      "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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description's only behavioral addition is 'takes no parameters', which the schema already shows, and it says nothing about freshness/caching of the model list or whether the catalog is dynamic across the open world.

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?

Three short sentences, front-loaded with the purpose and ending with the actionable instruction. The middle sentence restates the empty schema, which is mildly redundant, keeping it just under full marks.

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?

An output schema exists, so return-value shape need not be explained, and a no-parameter list tool needs little more than purpose and timing. The description covers both, though it omits any hint about catalog freshness or how returned IDs should be matched.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The statement 'This tool takes no parameters' reinforces what the empty schema already conveys but adds no new parameter meaning.

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?

States a specific verb and resource: 'List available DeepSeek models', with the added scope of 'for model selection and validation'. It loosely differentiates itself from the generation siblings by positioning itself as a pre-step to them, but it never names a specific sibling tool, so differentiation is directional rather than explicit.

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?

Explicitly gives a when-to-use condition: 'Use it before passing an explicit model ID to generation tools.' That is actionable guidance, though there is no when-not or named alternative (e.g., a cached static list), so it falls short of a full routing statement.

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

Deploy Server