fix(coderd/x/chatd): prevent nil required field in MCP tool schemas for OpenAI - #23538
Merged
Conversation
…or OpenAI
When an MCP server returns a tool whose inputSchema omits the
"required" field, the Go []string deserializes to nil. This nil
propagates through to the OpenAI API as "required": null, which
OpenAI rejects with "None is not of type 'array'".
Two fixes:
- mcpclient: coerce nil Required to []string{} in Info()
- chatloop: only include "required" key when non-empty
kylecarbs
marked this pull request as ready for review
March 24, 2026 21:53
ibetitsmike
approved these changes
Mar 24, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When an MCP server (e.g. Linear) returns a tool whose
inputSchemaomits therequiredfield, the Go[]stringdeserializes tonil. Thisnilpropagates through to the OpenAI API as"required": nullin JSON, which OpenAI rejects:Anthropic is unaffected because its provider defensively initializes
requiredto[]string{}. Fantasy's ownfuncToolWrapperalso has a nil guard, but the coder-sidemcpToolWrapperdid not.Two fixes:
Requiredto[]string{}inInfo(), matching what Fantasy'sfuncToolWrapperalready does."required"key in the schema map when non-empty, as defense-in-depth.