Skip to main content
Glama
pbandreddy

BlazeMeter MCP Server

by pbandreddy

get_test_run_aggregate_data

Retrieve aggregated performance test results for a specific test run to analyze metrics and identify issues.

Instructions

Get the aggregate report data for a specified test run (master).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
masterIdYesThe ID of the test run (master) to retrieve the aggregate report data for.

Implementation Reference

  • Core handler function that performs the HTTP GET request to the BlazeMeter API to retrieve aggregate report data for the given test run master ID, handles errors, and returns the data or error object.
    const executeFunction = async ({ masterId }) => {
      const baseUrl = process.env.BASE_URL; // loaded from .env
      const username = process.env.BZM_USERNAME; // loaded from .env
      const password = process.env.BZM_PASSWORD; // loaded from .env
    
      try {
        // Construct the URL for the aggregate report data
        const url = new URL(`${baseUrl}/api/v4/masters/${masterId}/reports/aggregatereport/data`);
    
        // Set up headers for the request
        const headers = {
          'Authorization': 'Basic ' + Buffer.from(`${username}:${password}`).toString('base64'),
          'Accept': 'application/json'
        };
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          let errorData;
          try {
            errorData = await response.json();
          } catch (jsonErr) {
            errorData = await response.text();
          }
          throw new Error(`HTTP ${response.status} ${response.statusText}: ${typeof errorData === 'string' ? errorData : JSON.stringify(errorData)}`);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        if (error instanceof Error) {
          return { error: error.message };
        } else {
          return { error: 'Unknown error occurred while getting aggregate report data.' };
        }
      }
    };
  • JSON schema definition for the tool, specifying the name, description, input parameters (masterId as required string), used for MCP tool listing and validation.
      type: 'function',
      function: {
        name: 'get_test_run_aggregate_data',
        description: 'Get the aggregate report data for a specified test run (master).',
        parameters: {
          type: 'object',
          properties: {
            masterId: {
              type: 'string',
              description: 'The ID of the test run (master) to retrieve the aggregate report data for.'
            }
          },
          required: ['masterId']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    Dynamic discovery and loading of all tools by importing apiTool from each file path listed in toolPaths, preparing the tools array for MCP server registration.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • mcpServer.js:40-80 (registration)
    Registers the MCP protocol handlers on the server for ListTools (listing tool schemas) and CallTool (executing the selected tool's function with input args, including validation), using the discovered tools.
    async function setupServerHandlers(server, tools) {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: await transformTools(tools),
      }));
    
      server.setRequestHandler(CallToolRequestSchema, async (request) => {
        const toolName = request.params.name;
        const tool = tools.find((t) => t.definition.function.name === toolName);
        if (!tool) {
          throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${toolName}`);
        }
        const args = request.params.arguments;
        const requiredParameters =
          tool.definition?.function?.parameters?.required || [];
        for (const requiredParameter of requiredParameters) {
          if (!(requiredParameter in args)) {
            throw new McpError(
              ErrorCode.InvalidParams,
              `Missing required parameter: ${requiredParameter}`
            );
          }
        }
        try {
          const result = await tool.function(args);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error("[Error] Failed to fetch data:", error);
          throw new McpError(
            ErrorCode.InternalError,
            `API error: ${error.message}`
          );
        }
      });
    }
  • List of all tool file paths relative to tools/, including the path to this tool's implementation file, used by discoverTools for loading.
    export const toolPaths = [
      'blazemeter/new-collection/get-workspace-list.js',
      'blazemeter/new-collection/get-project-list.js',
      'blazemeter/new-collection/get-test-runs-list.js',
      'blazemeter/new-collection/get-test-run-summary.js',  
      'blazemeter/new-collection/get-test-run-aggregate-data.js',
      'blazemeter/new-collection/get-test-run-errors-data.js',
      'blazemeter/new-collection/get-test-run-thresholds.js',
      'blazemeter/new-collection/get-test-run-timeline-kpis.js',
    ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Get[s]' data, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns paginated results, or details the format of the aggregate report data. This leaves significant gaps for a tool with no structured safety hints.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'aggregate report data' includes, how it differs from other test run data tools, or behavioral aspects like error handling. For a data retrieval tool with no output schema, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, clearly documenting the 'masterId' parameter. The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage without extra value.

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 verb 'Get' and the resource 'aggregate report data for a specified test run (master)', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_test_run_summary' or 'get_test_run_timeline_kpis', which likely retrieve different aspects of test run data, so it lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare to siblings such as 'get_test_run_summary', leaving the agent to infer usage from tool names alone.

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/pbandreddy/blazemeter-mcp-server'

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