Mcp tool schema update

[mariankrotil]

Before asking for review make sure that:

• you created a task for KBC team to update event-schema in Connection (validation in API endpoint)
• you notified everyone in #general that even schema is changing

[mariankrotil]

KBC team task https://keboola.atlassian.net/browse/CT-2220

[mariankrotil]

@Matovidlo Could you please notify in #general that mcp server tool event schema will be changed. And please review this PR and check my steps whether they are going the right direction.

[tomasfejfar]

Just one note - won't it fail for previous versions of MCP server which sends events without the requires param? The validation is strict in connection - either it matches the schema or it's refused.

[mariankrotil]

Just one note - won't it fail for previous versions of MCP server which sends events without the requires param? The validation is strict in connection - either it matches the schema or it's refused.

I was thinking the same. @ujovlado, @Matovidlo - how is this handled when we have old stored events and the schema gets updated? Will the missing values be adjusted, or should I make the field optional for backward compatibility?

[tomasfejfar]

The schema validates input in postMessage endpoint in connection. So if you update it and make it required, any request to create message without the serverTransport field will fail (HTTP 400). Normally that's OK, because we only update it after we release new version of the service that produces them. With MCP it's more complicated because we don't own the deployments (people have it potentially deployed locally, not updated).

[mariankrotil]

@tomasfejfar In that case, we should keep the field optional, right?

[mariankrotil]

@tomasfejfar The property is now optional and it should work with previous versions of mcp smoothly.

[ujovlado]

@tomasfejfar @mariankrotil

Why we kept both? Schemas for component keboola.mcp-server.tool are no longer needed, once this PR is released: keboola/mcp-server#251

[tomasfejfar]

If we want this fixed, let's do that in a new PR and new connection release. There is no problem releasing both schemas changed.