modelcontextprotocol / modelcontextprotocol/java-sdk
jsonschemabuilder
還沒有人認領這個 Issue。
- 主要語言
- Java
- 星號
- 3.7k
- 分支
- 1.1k
- 平均合併
- 1 天 15 小時
- 30 天內合併 PR
- 9
描述
Hopefully this is appropriate, prior, we were able to provide just a string to the includeSchema portion. Though I do like the approach of a type being passed now, I feel like the current JsonSchema object is too lax and doesnt really capture the needs. While working on my mcp server, I figured out that the best schema to provide was to just use the least common denominator approach, which is to use https://ai.google.dev/api/caching#Schema as the basis. Even though OpenAI's schema is better and does work for those llms that support it, gemini didnt conform to it well because it uses its own schema spec. So I built my own builder https://github.com/themixednuts/GhidraMCP/tree/main/src/main/java/com/themixednuts/utils/jsonschema
Is this something we can move towards?
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
審查 Java SDK 中目前的 includeSchema 和 JsonSchema API,然後將其與連結的 Google Schema 參考資料和 GhidraMCP builder 進行比較。完整的貢獻首先應確立較不寬鬆的 schema 模型之共識範圍,以及對 Gemini 和 OpenAI 的相容性預期。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- api, backend-api-design
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100