fix: all MCP tools now return a string response to increase compatibility

Author: evilsocket

src/mcp/service.rs

@@ -4,7 +4,7 @@ use std::time::Duration;
 use include_dir::{Dir, include_dir};
 use rmcp::handler::server::tool::{Parameters, ToolRouter};
 use rmcp::model::{ServerCapabilities, ServerInfo};
-use rmcp::{Json, ServerHandler, schemars, tool, tool_handler, tool_router};
+use rmcp::{ServerHandler, schemars, tool, tool_handler, tool_router};
 use tokio::sync::RwLock;
 
 const PLUGINS_DOCS_DIR: Dir = include_dir!("docs/plugins");
@@ -91,9 +91,9 @@ impl Service {
     }
 
     #[tool(description = "Get the number of currently available workers.")]
-    async fn get_available_workers(&self) -> Json<u64> {
+    async fn get_available_workers(&self) -> String {
         let guard = &*self.sessions.read().await;
-        Json(guard.get_available_workers())
+        format!("{}", guard.get_available_workers())
     }
 
     #[tool(

src/mcp/service_info.prompt

@@ -1,14 +1,16 @@
-This server provides an interface to Legba, a multiprotocol credentials bruteforcer / password sprayer and enumerator.
+Legba is a credentials bruteforcer, password sprayer and enumerator supporting several protocols with a dedicated plugin each.
 
-## Available Plugins
+## Supported Protocols Plugin Identifiers
 
 ##PLUGIN_LIST##
 
-- Use the plugin_info tool with the plugin identifier, as it is in this list, as it is to get information about a plugin, its options and how to use it.
+## Instructions
+
+- Use the `plugin_info` tool with the plugin identifier to get information about a plugin, its options and how to use it.
 - Some plugin identifiers (like HTTP) actually group multiple plugins, make sure to use the right one by using the examples as a reference.
-- Start a new session with the start_session tool.
-- Each session you start will use up the amount of workers you specify in --concurrency and free them once concluded. 
-- Use the get_available_workers tool to determine how many workers are available for use and wait if none is free.
+- Start a new session with the `start_session` tool.
+- Each session you start will use up the amount of workers you specify in `--concurrency` and free them once concluded. 
+- Use the `get_available_workers` tool to determine how many workers are available for use and wait if none is free.
 
 ## Arguments