Context We are currently running an MCP (Model Context Protocol) server that interfaces with Kiali. As the Kiali codebase evolves, there is a risk that the API routes, endpoint paths, or query parameters defined in Kiali's backend may change, causing the MCP tool definitions to become outdated and fail at runtime.

Objective Create an automated test suite that validates the consistency between the MCP tool definitions and the actual Kiali API implementation (specifically the route definitions and handler parameters).

Requirements

1. Endpoint/Route Verification:

• • The test should scan the MCP tools/list output.

• • For every MCP tool, verify that the underlying API path (URL) exists in the Kiali route definitions (e.g., checking routes.go or the OpenAPI/Swagger spec).

1. Parameter & Type Verification:

• • Verify that the arguments defined in the MCP inputSchema match the expected query parameters in Kiali.

• • Type Checking: Ensure that if Kiali expects an integer (e.g., limit), the MCP schema enforces an integer type, and if Kiali expects a specific string enum (e.g., graphType), the MCP schema reflects those valid options.