refactor(@angular/cli): add a get best practices guide MCP tool

[clydin]

The Angular CLI's stdio-based MCP server now contains a tool to get an Angular best practices guide. This is in addition to a resource with the same content. The tool provides a description that strongly encourages the use of this tool and its content when performing Angular related tasks. This is useful in cases where MCP resource usage is not available or the resource would need to manually be added as context for specific use cases.

[jkrems]

LGTM overall but I think we can skip the await?

[geromegrignon]

The Angular CLI's stdio-based MCP server now contains a tool to get an Angular best practices guide. This is in addition to a resource with the same content. The tool provides a description that strongly encourages the use of this tool and its content when performing Angular related tasks. This is useful in cases where MCP resource usage is not available or the resource would need to manually be added as context for specific use cases.

If the MCP resource usage refers to the compatibility matrix(https://modelcontextprotocol.io/clients#feature-support-matrix), from my attemps at doing about the same with Cursor, a content with type: "resource" exposed by a tool is still considered as a resource, resulting in a Content type "resource" not supported message

[clydin]

If the MCP resource usage refers to the compatibility matrix(https://modelcontextprotocol.io/clients#feature-support-matrix), from my attemps at doing about the same with Cursor, a content with type: "resource" exposed by a tool is still considered as a resource, resulting in a Content type "resource" not supported message

It was referring to UI mechanisms to add resources as context. However, to be safe the content is now text.

[clydin]

The changes were merged into the following branches: main, 20.1.x