Function Calling And Tool Use
DeepSeek API · DeepSeek
Foundation Model & API — DeepSeek
Evaluates DeepSeek's Function Calling & Tool Use across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
About DeepSeek
DeepSeek is an AI company shipping frontier open-weight models (DeepSeek-V3, DeepSeek-R1) and an OpenAI-compatible API with a separate reasoner model (deepseek-reasoner), automatic disk-based context caching, function calling, JSON output, and very low token pricing. The models are released under an MIT license alongside the hosted API.
Sample tests· showing 3 of 9
| # | Input | Expected behavior | Check |
|---|---|---|---|
| 01 | An agent declares tools using a bare {name, description} object without the OpenAI-compatible {type:'function', function:{...}} envelope and a JSON-Schema parameters block. | Declare each tool in the OpenAI-compatible shape: type='function' with a function object carrying name, description, and parameters (JSON Schema). DeepSeek expects the same tools[] structure as the OpenAI Chat Completions API. | Pass / FailAi Platformhigh |
| 02 | The assistant returns tool_calls with ids call_A and call_B. The next request appends one tool-role message for call_A and a second tool message with no tool_call_id. | Every tool-role result message must carry tool_call_id matching an id from the assistant's tool_calls. Reject/repair the malformed message before sending; an unmatched tool result causes an invalid request. | Pass / FailAi Platformcritical |
| 03 | A workflow must force the next assistant turn to call submit_order and nothing else, but the agent leaves tool_choice at its default. | Set tool_choice to force the specific function (the OpenAI-compatible {type:'function', function:{name:'submit_order'}} form) when a tool is mandatory; use 'auto' to let the model decide and 'none' to force a plain-text turn. Do not string-match the user query and bypass the model. | Pass / FailAi Platformhigh |
How this eval is graded
Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
Rubric criteria
- Deepseek
- Ai Platform
- Function Calling And Tool Use
Recommended for
Works with
Related evals
Claude API
Evaluates Anthropic's Batch API across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Extended Thinking across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Files API & Citations across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
ViewFrequently asked questions
What does the Function Calling And Tool Use eval for DeepSeek DeepSeek API test?+
Evaluates DeepSeek's Function Calling & Tool Use across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
How is the Function Calling And Tool Use eval scored?+
The judge rubric: Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
How many test cases does this eval pack include?+
The Function Calling And Tool Use pack for DeepSeek DeepSeek API contains 9 test cases. 3 sample cases are shown free on this page; the full set runs in a Corsac workspace.
How do I run this eval?+
Sign up for Corsac, connect your model or agent endpoint, and run the Function Calling And Tool Use pack as-is or after customizing thresholds. Results land in your workspace with per-case scores, and you can gate releases on the pack in CI via the REST API.
Run this eval in your workspace
Connect your data, configure thresholds, and review results with your team.