Skip to main content
Glama
pbandreddy

BlazeMeter MCP Server

by pbandreddy

get_test_run_summary

Retrieve a summary report for a specified BlazeMeter performance test run to analyze results and identify issues.

Instructions

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

Input Schema

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

Implementation Reference

  • The handler function that performs the HTTP GET request to the BlazeMeter API to fetch the summary report for the specified test run master ID.
    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 summary report
        const url = new URL(`${baseUrl}/api/v4/masters/${masterId}/reports/default/summary`);
    
        // 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 test run summary.' };
        }
      }
    };
  • Tool schema definition including the name, description, input parameters schema requiring 'masterId' string.
      type: 'function',
      function: {
        name: 'get_test_run_summary',
        description: 'Get the summary report for a specified test run (master).',
        parameters: {
          type: 'object',
          properties: {
            masterId: {
              type: 'string',
              description: 'The ID of the test run (master) to retrieve the summary for.'
            }
          },
          required: ['masterId']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    Dynamic registration loader that imports all tool modules listed in toolPaths and extracts their apiTool configurations.
    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);
    }
  • tools/paths.js:1-10 (registration)
    Central list of all tool file paths, including the path to get-test-run-summary.js, used by the discoverTools function.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying a read-only action, but doesn't clarify aspects like whether it requires authentication, has rate limits, returns structured or unstructured data, or if the summary is cached. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with the core action and resource, making it easy to parse. Every part of the sentence contributes essential information, earning its place.

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 for effective tool use. It doesn't explain what the summary report contains (e.g., metrics, status, or format), how it differs from sibling tools, or any behavioral traits like error handling. For a tool in a context with multiple similar siblings and no structured output, more detail is needed to guide the agent adequately.

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, with the parameter 'masterId' clearly documented. The description adds no additional semantic context beyond what the schema provides, such as explaining what a 'master' test run entails or format examples. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 action ('Get') and the resource ('summary report for a specified test run (master)'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'get_test_run_aggregate_data' or 'get_test_run_timeline_kpis', which likely retrieve different aspects of test run data, so it doesn't achieve full 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 what a 'summary report' includes compared to other test run data tools, nor does it specify prerequisites or exclusions. This leaves the agent with minimal context for selection among siblings.

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