module_request
Request a custom analysis module built for your specific business use case. Describe the analysis you need to get a tailored solution.
Instructions
Request a custom analysis module to be built for your use case.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| description | Yes | Describe the analysis you need |
Implementation Reference
- src/index.js:62-62 (registration)The tool 'module_request' is defined as a static catalog entry with a name, description, and input schema requiring a 'description' string. It is registered as part of the STATIC_TOOLS array (lines 43-63) which serves as both the fallback tool catalog and the list returned by ListToolsRequestSchema (line 117-119). However, the actual execution for 'module_request' (and all tools) is proxied through the remote MCP server via CallToolRequestSchema (lines 121-146). There is no local handler logic specific to 'module_request' — it is entirely forwarded to the remote API at https://api.mcpanalytics.ai/mcp.
{ name: "module_request", description: "Request a custom analysis module to be built for your use case.", inputSchema: { type: "object", properties: { description: { type: "string", description: "Describe the analysis you need" } }, required: ["description"] } }, - src/index.js:121-146 (handler)The CallToolRequestSchema handler proxies all tool calls (including 'module_request') to the remote MCP client. If no remoteClient is available, it returns an error asking for an API key. Otherwise, it forwards the tool name and arguments to remoteClient.callTool() and returns the result.
server.setRequestHandler(CallToolRequestSchema, async (request) => { if (!remoteClient) { return { content: [ { type: "text", text: "MCP Analytics API key required. Set MCP_ANALYTICS_API_KEY in your environment.\nGet a free key at https://app.mcpanalytics.ai", }, ], isError: true, }; } try { const result = await remoteClient.callTool({ name: request.params.name, arguments: request.params.arguments || {}, }); return result; } catch (err) { return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true, }; } }); - src/index.js:62-62 (schema)Input schema for 'module_request' defines a single required property 'description' (string) to describe the analysis the user needs.
{ name: "module_request", description: "Request a custom analysis module to be built for your use case.", inputSchema: { type: "object", properties: { description: { type: "string", description: "Describe the analysis you need" } }, required: ["description"] } },