>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3539318. --> Reported by: [jibla](https://www.drupal.org/user/1013184) Related to !25 >>> <p>Idea is to improve the tools naming that MCP module exposes for LLMS. This issue is basically for discussion and planning at the moment.</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Right now, tool names are the combination of the plugin id and the md5 hash. The reason for that is that we need the names to be unique and also some clients limit name lengths, so its good to have predictable lengths for tool names.</p> <p>Problem here is in two directions:<br> 1. Understanding for humans - when listing the tools exposed by Drupal MCP, there is no way to easily find out and understand what they are expected to do. You simply see the plugin id followed by the hash.</p> <p>2. Understanding for LLM clients - although there is a description there and it is the main thing that LLM uses to decide whether to use the tool or not (and to be honest, this works fine), having meaningful tool names could also help a lot, at least for some clients.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Enable MCP module with couple of plugins and you check the list of tools with LLM clients.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We need to discuss how to solve this. One possible way could be to maintain a separate mapping with unique ids and descriptive names. That would also require to manage the caching. Also having a way to manage it with MCP module's configuration (a new, improved version will be released soon hopefully), would be nice.</p>