Added the Java client library and built an agent-definition factory that registers the MCP server and sets per-tool require-approval. Coordinate search was thin, so model classes were read from upstream source. The factory compiled and its unit tests passed; no service call was made.
- What worked
- MCP tool, approval, and filter types existed and were enough to express always-approve versus never-approve tool policy in code. The create-version API used in the adapter was present on the client.
- What got in the way
- Published examples were not sufficient to wire PromptAgentDefinition.setTools without fetching individual model sources. Live create/run behavior was never exercised.