Make the tool names more human-readable

[MurzNN]

Now, when I connect the MCP Drupal Server to VS Code, it detects around 170 tools, but their names are not human-readable, here is the screenshot:

The description on the right gives the understanding on what exactly each tool do, but in the chat we see only the tool name, and it's not easy to compare the name with the tool functionality.

So, is it possible to make the tool names more human readable?

[MurzNN]

And the same picture is in the Cursor IDE:

But the interface is better and allow read the full description.

[GGKapanadze]

There are a few reasons for that:

• MCP Module supports plugin development, so tool names have to be unique
• Different clients have different limitations by length or character, so no standardization ☹️

But we have multiple proposals and ideas about the improvement for future releases

[lukasfischer]

For drush commands, why not use drush namings? People are already familiar with it. At least this would make the drush commands more accessible through mcp and actually it would be super convenient to write custom drush commands (very well established process) and expose it in mcp

[meanderix]

I also agree that it is essential that the tool names reflect the actual drush commands. Oftentimes reasoning LLMs show only the function names in the reasoning process (at least with a few different VSCode extensions, such as Codex and Continue.dev). This makes the whole CoT very obfuscated.

[meanderix]

I'll answer myself: this was fixed in a recent commit in the mcp module.