What Happened?
The current DeepSeek provider implementation does not support tool/function calling. While other providers expose tool execution through the standard tooling interface, DeepSeek responses are currently limited to plain text generation. This prevents agents or workflows that rely on tool invocation from functioning correctly when the DeepSeek model is used.
What Should Have Happened?
Expected Behavior
DeepSeek models should support tool/function calling similar to other providers. The response parser should detect tool call instructions from the model output and route them through the existing tooling pipeline.
Relevant Code Snippet
Current Behavior
- Tool calls are not detected in DeepSeek responses.
- No tooling execution is triggered.
- Agent workflows that depend on tools fail or fall back to text responses.
Steps to Reproduce
- Configure DeepSeek as the LLM provider.
- Register one or more tools in the agent/tooling system.
- Send a prompt that requires tool usage.
- Observe that the model returns a text response instead of triggering a tool call.
Your Twitter/LinkedIn
No response
What Happened?
The current DeepSeek provider implementation does not support tool/function calling. While other providers expose tool execution through the standard tooling interface, DeepSeek responses are currently limited to plain text generation. This prevents agents or workflows that rely on tool invocation from functioning correctly when the DeepSeek model is used.
What Should Have Happened?
Expected Behavior
DeepSeek models should support tool/function calling similar to other providers. The response parser should detect tool call instructions from the model output and route them through the existing tooling pipeline.
Relevant Code Snippet
Current Behavior
Steps to Reproduce
Your Twitter/LinkedIn
No response