Feature/version tools - adding 2 new tools, get latest provider and module versions#122
Feature/version tools - adding 2 new tools, get latest provider and module versions#122gautambaghel merged 3 commits intomainfrom
Conversation
| } | ||
|
|
||
| func getLatestProviderVersionHandler(registryClient *http.Client, request mcp.CallToolRequest, logger *log.Logger) (*mcp.CallToolResult, error) { | ||
| namespace, err := request.RequireString("namespace") |
There was a problem hiding this comment.
when i built mine, i was wondering if we should just default to hashicorp since that would be most often correct if the llm doesn't know it.
i also wonder if we want to lower-case all the input to normalize it. should test for this too.
There was a problem hiding this comment.
defaulting to hashicorp stops the model from thinking and ends up calling the tools twice, it's better to add it in the description (saying e.g, hashicorp - which we've done) that way if it has no other choice it uses hashicorp. hashicorp owns <20 providers, we got at least 200 decent providers out there
the APIs are case insensitive, but should be easy to add
There was a problem hiding this comment.
good points. totally agree the description covers it well enough.
2 participants
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.