Trial to make a more explicit json export

[rsandell]

I saw that the tools just returned a string of json instead of actual json. So this was a test to try to do a more explicit export to json.

But the result seems to be the same, so I thought I'd just leave it here for prosperity.

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[topikachu]

@rsandell
I'm going to integrate with the new Java MCP SDK, which supports structured output.
However, the implementation is currently blocked by issue #584.

Since the issue has been fixed and will be included in the upcoming v0.15.0 release, we’ll wait for that version and then leverage the built-in Output Schema capability.

Thanks

[olamy]

@topikachu good idea. more generally I was thinkig about reworking the output especially for empty result.
Something such Result is null might be a bit confusing for Agent/LLMs. (something wrong or it's just no result)

I was thinking about more structured reponse.

Results found

{
  "status": "completed",
  "message": "Data retrieved successfully.",
  "result": [
    {
      "id": "123",
      "name": "Example Item"
    },
    {
      "id": "456",
      "name": "Another Item"
    }
  ]
}

All good but no result

{
  "status": "completed",
  "message": "Search completed, but no results were found for the specified criteria.",
  "result": []
}

Errors

{
  "status": "failed",
  "message": "The provided parameters are invalid.",
  "error": {
    "code": "INVALID_PARAMETERS",
    "details": "The 'date' parameter must be in YYYY-MM-DD format."
  }
}

the format is just an idea we can have different general format of course.

[olamy]

I have created a separate issue for this #82