Is right to call Microservice a project that is just an adapter?

Let's think I have a project that manage games. In this project, I use request X for example.

But I had to create a new project to use request Y. We can think that is to be conformed with some standards of API for games manager. In this new project, I only have mapping being done. The project that uses request Y change the request to X and call the API. There is no business logic, only mapping logic. So, we can see that new project is a kind of adapter. In this new project I have a different development, deployment and team managing.

My question is: is right to call the new project of microservice? The new one is highly coupled of the core (the one that manage games) and doesn't work without it.