[v6.0] fix: include object type in default tool schema#16799
Merged
Conversation
OpenAI-compatible providers such as DeepSeek can strictly validate tool parameter schemas and require them to be JSON Schemas with type: "object". When a tool does not define an input schema, asSchema(undefined) produced an empty object-shaped schema with properties and additionalProperties, but without the explicit type: "object". That caused those providers to reject tool definitions even though the SDK intended to send an empty object schema. Add type: "object" to the default schema created by asSchema(undefined). Add a regression test covering the default empty schema behavior. Add a patch changeset for @ai-sdk/provider-utils. Fixes #7924 Recreates #15163 with commit signatures (cherry picked from commit 105f95b)
gr2m
added
the
backport
github-actions
Bot
removed
the
backport
Contributor
|
|
Contributor
|
🚀 Published in:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #15249 to
release-v6.0. When a tool defines no input schema,asSchema(undefined)now produces a default schema with an explicittype: "object", so strict OpenAI-compatible providers (e.g. DeepSeek) no longer reject tool definitions with empty parameter schemas. The only conflict was inpackages/provider-utils/src/schema.test.ts, where the newasSchemaregression test block was inserted at the top of the file adjacent to unrelated surrounding test changes on main; the test was ported verbatim (includingawait schema.jsonSchema, which is valid in v6 sincejsonSchemamay be aPromiseLike). The changeset from the original commit is kept. Part of the v6.0 backport tracking issue #16767.