Skip to main content
Glama

module_request

Request custom analysis modules for business data from platforms like Shopify, Stripe, and GA4. Submit your specific analysis needs to receive tailored interactive HTML reports.

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

  • The codebase is a proxy that dynamically fetches all tools from a remote server. The 'module_request' tool is not explicitly defined in the code; it is fetched from the remote server at runtime (lines 80-86) and then handled generically by the CallToolRequestSchema request handler, which forwards the call to the remote client.
    // tools/call — forward to the remote server
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      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,
        };
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only hints at asynchronous behavior ('to be built'). It lacks critical disclosure: whether this creates a ticket, requires human review, incurs costs, or how the user gets notified when complete.

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

Conciseness4/5

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

The single-sentence description is efficiently structured and front-loaded with the core action. However, extreme brevity becomes a liability given the lack of annotations and the significant nature of requesting custom development.

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?

For a tool initiating what appears to be a complex workflow (custom module development), the description is inadequate. No output schema exists, and the description fails to explain expected outcomes, response format, or next steps in the process.

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 has 100% coverage for the single 'description' parameter. The description adds minimal semantic context beyond the schema, merely framing it as a request for custom work rather than enriching the parameter's expected content or format.

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

Purpose4/5

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

The description clearly states the tool requests a custom analysis module using specific verb (request) and resource (custom analysis module). It implies creation of something new versus using existing tools, though it could more explicitly distinguish from siblings like 'tools_run' or 'reports_view' that use existing capabilities.

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 provided on when to use this versus existing analysis tools, no mention of prerequisites (approvals, billing implications), and no indication of expected timeline or process for module delivery.

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