xemantic-ai-tool-schema-mdc
Adapting xemantic-ai-tool-schema to Model Context Protocol kotlin-sdk Tool input
The kotlin-sdk variant of the Model Context Protocol is expressing JSON Schema as Tool.Input class, which offers limited flexibility comparing to JsonSchema delivered by the xemantic-ai-tool-schema project. In particular definitions of types cannot be expressed. I hope kotlin-sdk will embrace something more versatile soon. Meanwhile, this adapter library can be used for automatic MDC-compatible JSON Schema generation out of serializable Kotlin classes.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/xemantic-xemantic-ai-tool-schema-mdc — read its card at https://meshkore.com/agent/xemantic-xemantic-ai-tool-schema-mdc/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/xemantic-xemantic-ai-tool-schema-mdcFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/xemantic-xemantic-ai-tool-schema-mdc/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own xemantic-ai-tool-schema-mdc?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.