Skip to main content
Glama
deepseek-mcp-server

deepseek-mcp-server

DeepSeek server status and self-test

deepseek_status

Displays resolved configuration with masked API key, request statistics, and session count; optionally runs a live test call to verify key, base URL, and network path for troubleshooting.

Instructions

Show the resolved configuration (API key masked), request statistics for this process, and session count. Pass test_connection to make a live one-token call that verifies the key, base URL and network path end to end. Run this first whenever something is not working.

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": "deepseek_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_connectionNoMake a real minimal API call to verify connectivity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses that the API key is masked, that statistics are scoped to "this process," and that test_connection performs a real one-token call touching key, base URL, and network path. It omits what a failed test looks like or whether the live call has cost/rate implications.

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 sentences, front-loaded with what is returned, then the optional live check, then the triage rule. No filler and no repetition of the title.

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 single-boolean tool with no output schema, the description lists the three return categories, which is enough to know what comes back. It does not describe the shape of the output when test_connection is set (success/failure detail), a minor gap given no output schema exists.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema's "real minimal API call": it names exactly what is verified (key, base URL, network path end to end) and that it is a one-token call. This helps the agent decide whether to pay that cost.

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 (Show) plus three concrete outputs — masked configuration, per-process request statistics, and session count — and adds an optional live connectivity check. This clearly separates it from siblings like deepseek_balance, deepseek_models, or deepseek_chat.

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?

"Run this first whenever something is not working" gives an explicit diagnostic trigger, which is real usage guidance. It stops short of naming alternative tools for specific failure modes (e.g., use deepseek_models for model listing), but the triage directive is clear.

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