[WIP] feat: add IsValid check for toolsets

[Cali0707]

This PR allows us to dynamically enable/disable toolsets, as well as the targets within tools, based on whether or not prerequisites for the toolset are installed in a given target cluster.

That way, users can enable e.g. kiali toolset, and if it is only installed in 3/4 clusters, we will only hint targets for those 3 clusters to the MCP client. Similarly, if none of the clusters have kiali installed, we will simply disable the toolset and not present it to any clients.

[Cali0707]

@aljesusg when you have time can you take a look at this method and let me know if this makes sense?

It's supposed to validate that there is a working kiali installation in the target cluster

[aljesusg]

Yes… although I would do the following: since the AuthInfoEndpoint endpoint is already created, I would create a method to call it, as it doesn’t require any parameters and is ‘available’ whether the user is authenticated or not.

[Cali0707]

Will add tests to this next, then it should be good to merge (if people like the approach here)

[manusa]

I believe that this entire functionality requires more thought.

This is similar to what's already done in:

kubernetes-mcp-server/pkg/api/toolsets.go

Line 46 in 0e88935

GetTools(o internalk8s.Openshift) []ServerTool

and related methods/functons.

Note

This was part of the first spike of the MCP server hence it doesn't make sense in the current state of the cluster.

In the early stages of the Kubernetes MCP server this was just enough:

• The MCP server was supposed to connect to a single cluster
• The MCP server ran with a root user that could access most cluster resources (allow for inference of an OpenShift cluster)
• The eventually authorized user might have a subset of the available cluster resources but that was fine since the listed tools were tailored for the vanilla Kubernetes or OpenShift experience based on the cluster-wide accessible resources discovered by the root user.

In the current state (multi-cluster + auth support), when a user/client performs a list request (tools, prompts, and so on), the MCP server SHOULD account for everything that applies to that user in its specific scenario:

• Accessible clusters (might be of different flavors)
• API extensions/Operators available in each cluster (each cluster might have a different set of operators installed)
• APIs accessible by the user (each user might have different RBAC settings that prevent them from accessing a given set of resources)

I'm not convinced about the idea of completely enabling or disabling an entire toolset (as this PR proposes).
Consider the core toolset which has tools to retrieve metrics, ideally, we should be able to detect if the metrics server is available, and then present the tool to the user only if the resource is in the cluster.

One of the challenges to do this properly is that go-sdk (or any of the other SDKs) require the tools to be loaded at start-up and don't provide callbacks to provide the tool or resource list dynamically or per session/user (AFAIK, maybe this has changed).

In this PR we're getting the derived Kubernetes when reloading the tools, but this will likely fail if there's no global auth for that cluster.

I'm really not sure how the problem can be properly tackled. Maybe checking the internals of the SDK and seeing if the list/tools request can be intercepted or something along those lines.