Allowing MCP server to discover and call available Angular schematics

### Command

mcp

### Description

Today, when I'm using LLM with the Angular MCP server, code is generated directly by the LLM but for some cases it would provide better result if it is using the available schematic (Angular ones or external libraries ones).

### Describe the solution you'd like

When using the Angular MCP server, I would expect LMM to be aware of which Angular schematics are available in the project (the ones from Angular + the ones from external libraries).
I would love that the Angular MCP server is able to read the schematic description and input, to know if it should use it or not and how to call it.

### Describe alternatives you've considered

_No response_

Comienza con el comando `mcp` de Angular CLI y sigue cómo el servidor MCP expone herramientas. Revisa cómo se describen y se invocan los schematics de Angular y los schematics externos; se considera terminado cuando el servidor puede descubrir los schematics de proyecto disponibles, exponer sus entradas y llamar a un schematic seleccionado.

Escrito por el modelo de indexación a partir del texto del issue.