MCP Server CD2 Iteration 2 (Continuous Delivery) – Release Notes

In this document:

Upgrade Notes

Groovy Tool Schema Validation

With the introduction of nested property support (PFS-233), the MCP Server now performs stricter validation on the inputSchema of Groovy tools. Only standard JSON Schema primitives (e.g., integer, string, boolean) are allowed. Non-standard types, such as int, will now be rejected during initialization.

Regression Risk

Existing Groovy tools using incorrect types in their inputSchema will fail validation. This causes the associated MCP role to fail initialization, and the affected tools will be reported as "missing." For example, the legacy parameters_list tool may fail if its nResults property type is set to int instead of integer.

Error Message Example

Failed to initialize MCP role "Object Fetcher" due to missing tools on the MCP server. Expected tools: fetch_objects and parameters_list. Received tools: fetch_objects (Missing tools: parameters_list).

Mitigation Steps

1. Review all custom Groovy tools and ensure their inputSchema uses standard JSON Schema types (e.g., change type: "int" to type: "integer").

2. Validate tool schemas against a development instance of the new MCP Server version before upgrading production environments.

3. Remove or refactor deprecated legacy tools, such as parameters_list, if they are no longer required by your current deployment.

Improvements