-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
-
False
-
Not Selected
-
-
-
-
Rox Sprint 4.11A, Rox Sprint 4.11B
User or Developer story:
Currently, all tools support filtering only by cluster ID. This causes problems where a user provides a cluster name, and in that case AI Agent has to call list_clusters tool first to get mapping between cluster names and IDs. After that AI Agent can call other tools with a provided cluster ID for filtering.
We would eliminate calling of two tools if we would provide filtering by cluster name within existing tools that are using filtering by cluster ID. Because in that case, the AI Agent can directly call a tool with provided cluster name.
Acceptance Criteria:
- add filter by cluster name to all existing tools (nodes, deployments, and orchestrator components)
- (optional) AI agent should validate if cluster name is not correct
Additional Info
- AI Agent cluster name validation
We should add in description of option (ideally), if that option is used and MCP didn't return any data, to check if provided cluster name is valid by calling list_clusters tools.
In this case we have again two calls, but it is conditional.