Different tools use different capabilities of the Cryostat API, which may have been introduced at different Cryostat server version levels. Since the MCP would be distributed separately from the server and may be used to interface with various Cryostat instances, it may need to interact with different Cryostat versions. There is already a Cryostat server health tool which the LLM can use to determine the Cryostat server version, so adding tags to each tool with the minimum Cryostat API level (or API version range) should help ensure that LLMs only try to use tools which are applicable to the Cryostat instance the MCP is configured to connect to.
Different tools use different capabilities of the Cryostat API, which may have been introduced at different Cryostat server version levels. Since the MCP would be distributed separately from the server and may be used to interface with various Cryostat instances, it may need to interact with different Cryostat versions. There is already a Cryostat server health tool which the LLM can use to determine the Cryostat server version, so adding tags to each tool with the minimum Cryostat API level (or API version range) should help ensure that LLMs only try to use tools which are applicable to the Cryostat instance the MCP is configured to connect to.