Skip to main content
Glama
DMontgomery40

DeepSeek MCP Server

completion

Generate fill-in-the-middle text completions from a prompt and optional suffix, returning raw completion text for code and content workflows. Configure model, temperature, and other generation parameters as needed.

Instructions

DeepSeek V4 Pro FIM completion tool for prompt/suffix fill-in-the-middle workflows. Defaults to deepseek-v4-pro. Use this when you need raw completion text instead of chat message formatting. Set include_raw_response=true only when you need the full provider payload for debugging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
echoNo
stopNo
modelNodeepseek-v4-pro
top_pNo
promptYes
streamNo
suffixNo
logprobsNo
extra_bodyNo
max_tokensNo
temperatureNo
presence_penaltyNo
frequency_penaltyNo
include_raw_responseNo
Install Server

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must cover behavior. Only mentions model default and include_raw_response usage, but lacks details on response format, limits, or side effects.

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-loading purpose and usage, zero wasted words. Efficient and well-structured for quick comprehension.

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

Completeness2/5

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

Despite clear purpose, the description is insufficient for a tool with 14 parameters and no output schema. Missing parameter meanings and response semantics.

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

Parameters1/5

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

With 0% schema description coverage and 14 parameters, description only addresses 'model' and 'include_raw_response' marginally. No information on other parameters.

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?

Clearly states it's a FIM completion tool for prompt/suffix workflows, contrasts with chat formatting, and specifies the default model. Differentiates from sibling 'chat_completion'.

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 tells when to use (raw completion vs chat) and when to set 'include_raw_response'. Does not explicitly state when not to use but provides clear context.

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

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

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