DeepSeek's official Tool Calls docs now pin a strict-beta schema path, supported JSON Schema subset rules, and explicit `tool` role replay requirements

Checked on June 29, 2026: DeepSeek's official Tool Calls guide documents OpenAI-compatible function calling, a Beta-only `strict` mode for exact schema matching, concrete supported and unsupported JSON Schema rules, and a required `tool` role replay pattern after execution.

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses a current official DeepSeek documentation page because the official @deepseek_ai X timeline still was not safely readable in this run. DeepSeek's English homepage continues to anchor the official X account, but the direct timeline did not expose a reliably crawlable current post here, so the publish-safe choice is a first-party docs-backed developer update.

What we verified on June 29, 2026

DeepSeek's official Tool Calls guide now documents a full OpenAI-compatible function-calling contract for chat completions, including tools definitions and tool_calls output in assistant responses.
The same page adds a stricter beta path: you can set strict: true on a function schema for more precise argument matching, but the docs mark that mode as Beta and require the Beta base URL.
DeepSeek publishes a concrete schema support boundary for strict mode: supported types are string, number, integer, boolean, object, array, enum, and anyOf.
The same strict-mode note also lists unsupported schema features such as minLength, maxLength, pattern, format, minimum, maximum, multipleOf, patternProperties, and array bounds like minItems and maxItems.
The replay contract after execution is concrete: callers should append the assistant message that contains the tool call, then append a tool role message with the returned result before asking the model for the next turn.

Why this is publishable

This is a current official DeepSeek API capability check, not a rumor, repost, or inventory claim.

It answers real implementation questions for agent and workflow builders: schema strictness, supported JSON Schema shapes, and correct replay order.
It stays clearly inside official facts and avoids guessing about undocumented behavior.
It is distinct from the June 27 stateless-history item because the story here is tool orchestration and schema enforcement, not general conversation replay.
It does not imply any new stocked plan card, resale entitlement, or inventory change on /pricing.

Why this matters for DeepSeek-first SEO pages

Support pages can now target DeepSeek tool calls strict mode with first-party wording instead of generic OpenAI function-calling assumptions.
Agent builders can separate tool replay bugs from history replay bugs, which are related but not the same failure class.
DeepSeek-first coding pages can explain which strict-schema constraints are actually supported today instead of overpromising full JSON Schema coverage.

Rejected candidates today

Official X timeline as the primary source: rejected for this run because the homepage still anchored DeepSeek's X presence, but the direct X surface remained unreadable here.
The homepage V4 Preview X anchor: official, but older and already represented by existing launch and migration coverage.
Chat Prefix Completion (Beta): official and useful, but stronger as a focused support-query guide than as the one daily news headline.
FIM Completion (Beta): official and useful, but narrower and better suited to code-completion long-tail coverage than the single daily news slot.
Models & Pricing, Rate Limit, status, GitHub, and Hugging Face surfaces: checked as backup official sources, but no stronger current update beat the Tool Calls contract for today's single publish-safe news slot.

Editorial takeaway

The safest official DeepSeek story today is a tool-calling contract check: the current docs define how DeepSeek handles tools, where strict schema matching still stays Beta-only, which JSON Schema constraints are actually supported today, and how callers must replay tool results back into the conversation. That is a stronger current developer signal than recycling an older X anchor we still could not fully verify live.