Some model providers support strict json output, meaning the llm will call the tool with the exact schema provided. I have seem some cases where it is mixing up cases (using snake case vs camelcase) or passing null to required fields. Call id: f13bc596-b901-4f48-bcb4-ffc2a12a1304 (On this one you can see the firstName being passed as null, but is required on the schema)

@Nomadiction I'm sorry to hear that there have been issues with the structured data not adhering to the specified schema. It's important that the data follows the correct format, including the case sensitivity of the keys and the handling of required fields. For the call ID you've provided, I will need to look into the specific details of the schema and the data that was passed. If there is a discrepancy, we will need to address this to ensure that the structured data is correctly formatted according to the schema requirements. Please hold on while I investigate the issue with the call ID f13bc596-b901-4f48-bcb4-ffc2a12a1304 and the

firstName

field being passed as null. If you have the schema available, could you please provide it? This will help me to understand the exact requirements and assist you better.

@Nomadiction try explicitly stating the input parameters your are expecting the tool required, also change your tool description including purpose, usage and expected input parameters under 320 characters.