Skip to main content
Glama
pbandreddy

LoadRunner Cloud MCP Server

by pbandreddy

projects_getLoadTests

Retrieve load tests for a project from LoadRunner Cloud to analyze performance test data and manage testing workflows.

Instructions

Retrieve load tests for a project from LoadRunner Cloud.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project.

Implementation Reference

  • The handler function `executeFunction` that performs the API call to retrieve load tests for a given projectId from LoadRunner Cloud.
    const executeFunction = async ({ projectId }) => {
      const baseUrl = process.env.LRC_BASE_URL;
      const tenantId = process.env.LRC_TENANT_ID;
      const token = await getAuthToken();
      try {
        // Construct the URL with query parameters
        const url = new URL(`${baseUrl}/projects/${projectId}/load-tests`);
        url.searchParams.append('TENANTID', tenantId);
    
        // Set up headers for the request
        const headers = {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${token}`
        };
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const text = await response.text();
          try {
            const errorData = JSON.parse(text);
            throw new Error(JSON.stringify(errorData));
          } catch (jsonErr) {
            // Not JSON, log the raw text
            console.error('Non-JSON error response:', text);
            throw new Error(text);
          }
        }
    
        // Parse and return the response data
        const text = await response.text();
        try {
          const data = JSON.parse(text);
          return data;
        } catch (jsonErr) {
          // Not JSON, log the raw text
          console.error('Non-JSON success response:', text);
          return { error: 'Received non-JSON response from API', raw: text };
        }
      } catch (error) {
        console.error('Error retrieving load tests:', error);
        return { error: 'An error occurred while retrieving load tests.' };
      }
    };
  • Input schema defining the required 'projectId' parameter as a string.
    parameters: {
      type: 'object',
      properties: {
        projectId: {
          type: 'string',
          description: 'The ID of the project.'
        }
      },
      required: ['projectId']
    }
  • tools/paths.js:1-11 (registration)
    The toolPaths array includes the path to this tool's file, enabling its dynamic loading.
    export const toolPaths = [
      'loadrunner-cloud/load-runner-cloud-api/projects-get-projects.js',
      'loadrunner-cloud/load-runner-cloud-api/test-runs-get-active-test-runs.js',
      'loadrunner-cloud/load-runner-cloud-api/test-runs-get-test-run-transactions.js',
      'loadrunner-cloud/load-runner-cloud-api/test-runs-get-test-run-summary.js',
      'loadrunner-cloud/load-runner-cloud-api/test-runs-get-http-responses.js',
      'loadrunner-cloud/load-runner-cloud-api/test-runs-get-test-run-recent.js',
      'loadrunner-cloud/load-runner-cloud-api/projects-get-load-tests.js',
      'loadrunner-cloud/load-runner-cloud-api/projects-get-load-test-scripts.js',
      'loadrunner-cloud/load-runner-cloud-api/projects-get-load-test-runs.js'
    ];
  • lib/tools.js:7-16 (registration)
    The `discoverTools` function dynamically imports all tools from toolPaths and spreads their apiTool exports to register them.
    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);
    }
  • Supporting `getAuthToken` function used by the handler to obtain authentication token for API requests.
    const getAuthToken = async () => {
      const baseUrl = process.env.LRC_BASE_URL;
      const tenantId = process.env.LRC_TENANT_ID;
      const clientId = process.env.LRC_CLIENT_ID;
      const clientSecret = process.env.LRC_CLIENT_SECRET;
    
      try {
        const url = new URL(`${baseUrl}/auth-client`);
        url.searchParams.append('TENANTID', tenantId);
    
        const headers = {
          'Content-Type': 'application/json',
          'accept': 'application/json'
        };
    
        const body = JSON.stringify({
          client_id: clientId,
          client_secret: clientSecret
        });
    
        const response = await fetch(url.toString(), {
          method: 'POST',
          headers,
          body
        });
    
        if (!response.ok) {
          const text = await response.text();
          try {
            const errorData = JSON.parse(text);
            throw new Error(JSON.stringify(errorData));
          } catch (jsonErr) {
            // Not JSON, log the raw text
            console.error('Non-JSON error response:', text);
            throw new Error(text);
          }
        }
    
        const data = await response.json();
        // Adjust according to actual API response structure
        return data.access_token || data.token || data;
      } catch (error) {
        console.error('Error retrieving auth token:', error);
        return { error: 'An error occurred while retrieving auth token.' };
      }
    };
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. It states the action is 'Retrieve', implying a read-only operation, but does not disclose behavioral traits such as authentication requirements, rate limits, pagination, or what happens if the project ID is invalid. This is inadequate for a tool with no annotation coverage.

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, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

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 complexity of retrieving data with no annotations and no output schema, the description is incomplete. It lacks details on return values (e.g., what load tests include), error handling, or prerequisites, which are crucial for an agent to use the tool effectively in context with siblings.

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 'projectId' documented as 'The ID of the project.' The description does not add any meaning beyond this, such as format examples or constraints, so it meets the baseline score of 3 for high schema coverage.

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 ('Retrieve') and target resource ('load tests for a project'), making the purpose understandable. However, it does not differentiate from sibling tools like 'projects_getLoadTestRuns' or 'projects_getLoadTestScripts', which appear to retrieve related but different resources, so it misses 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. With siblings like 'projects_getLoadTestRuns' and 'projects_getLoadTestScripts', there is no indication of what distinguishes this tool (e.g., retrieving load tests vs. runs or scripts), leaving usage unclear.

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/loadrunner-cloud-mcp-server'

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