Skip to main content
Glama

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

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesDescribe 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"] } },
  • 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,
        };
      }
    });
  • 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"] } },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; the description does not disclose any behavioral traits such as processing time, response format, or permissions required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but omits valuable context; trade-off between brevity and completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description should explain what happens after requesting a module (e.g., approval process, timeline). It does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no additional meaning to the single 'description' parameter beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (Request), the resource (custom analysis module), and the context (for your use case). It distinguishes from sibling tools like tools_run which execute existing modules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, nor any prerequisites or expected outcomes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/embeddedlayers/mcp-analytics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server