Replies: 5 comments 2 replies
-
|
That error means your API is returning null for a field that the schema says isn’t nullable, and is being evaluated in the low level SDK so we can’t improve the error message. If you can confirm that the schema says nullable and FastMCP is incorrectly changing to non-nullable, then we can address. We have a new test suite for this specific issue. Otherwise this is an issue with the API itself which we’ve also seen. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
As I said, this is not being raised in FastMCP, it's being raised by the schema validation in the low-level SDK, which was bumped between FastMCP 2.10 and FastMCP 2.11. Keep in mind, |
Beta Was this translation helpful? Give feedback.
-
|
@jlowin I ran into the same thing. Is there any way to get any detail as to where the validation failed? I have a giant response with 40 properties |
Beta Was this translation helpful? Give feedback.
-
|
Probably a dupe of #1385, I can confirm Tenable doesn't define nullable where null values might appear, so there needs to be a compatibility option. |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @jlowin , Is openapi 3.0.x really supported with fastmcp 2.11.x version. As I just tried openapi 3.0.x api specification and I am still seeing input schema validation error.
Error- when calling tool
Input validation error: None is not of type 'string'
Schema example I am trying - (Note - I have verified my openapi 3.0.x schema using swagger online editor, and there things are ok)
Beta Was this translation helpful? Give feedback.
All reactions