The toolset processing logic is missing a call togithub.CleanToolsets() that exists in the stdio command (seeinternal/ghmcp/server.go line 102). This function:

1. Removes whitespace from toolset names
2. Removes duplicates
3. Validates toolset names and identifies invalid ones

Without this, the command may behave inconsistently with the stdio command when users provide invalid or malformed toolset names. Add the CleanToolsets call before processing special keywords:

// Clean up the passed toolsetsenabledToolsets,invalidToolsets:=github.CleanToolsets(enabledToolsets)// Optionally warn about invalid toolsets (like server.go does)iflen(invalidToolsets)>0 {fmt.Fprintf(os.Stderr,"Invalid toolsets ignored: %s\n",strings.Join(invalidToolsets,", "))}// If "all" is present, override all other toolsetsifgithub.ContainsToolset(enabledToolsets,github.ToolsetMetadataAll.ID) {enabledToolsets= []string{github.ToolsetMetadataAll.ID}}// ...

The manual deduplication ofacceptedScopeStrs using nested loops is O(n²) and could be simplified for better maintainability and performance. Consider using a map for deduplication:

// Calculate accepted scopes (scopes that also satisfy the requirement due to hierarchy)acceptedScopeMap:=make(map[string]bool)for_,reqScope:=rangerequiredScopes {accepted:=scopes.GetAcceptedScopes(reqScope)for_,accScope:=rangeaccepted {ifaccScope!=reqScope {// Don't duplicate the required scopeacceptedScopeMap[accScope.String()]=true        }    }}acceptedScopeStrs:=make([]string,0,len(acceptedScopeMap))forscope:=rangeacceptedScopeMap {acceptedScopeStrs=append(acceptedScopeStrs,scope)}sort.Strings(acceptedScopeStrs)

This approach is more efficient and clearer in intent.

[nitpick] The conditional build check may not detect all necessary rebuilds (e.g., when dependencies in other packages change). For consistency with other scripts likescript/generate-docs, consider usinggo run instead:

exec go run ./cmd/github-mcp-server list-scopes"$@"

This approach is simpler, always ensures up-to-date code execution, and aligns with the project's script patterns. The build time overhead is minimal (~1s according to the guidelines).