Skip to main content
Glama
IAnjaniKr

jmeter-mcp-server

by IAnjaniKr

create_test_plan_from_api_source

Generate a JMeter test plan from an OpenAPI file or explicit endpoint details, with configurable test profiles, assertions, and output file.

Instructions

Create a JMeter test plan from an API source. Supported sourceType values: openapi, endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoFor sourceType=endpoint: raw request body
nameNoOptional JMeter test plan name
pathNoFor sourceType=endpoint: request path, e.g. /v1/users
loopsNoLoop count; use -1 for forever. For deterministic profiles, omit or match the policy value.
usersNoRequired only for testProfile=custom. For deterministic profiles, omit or match the policy value.
methodNoFor sourceType=endpoint: HTTP method
envFileNoFor sourceType=openapi: optional .env file used for auth/data defaults
headersNoFor sourceType=endpoint: request headers
rampTimeNoRamp-up time in seconds. For deterministic profiles, omit or match the policy value.
serverUrlNoFor sourceType=endpoint: base server URL, e.g. https://api.example.com
outputfileYesPath where to save the .jmx file
sourceFileNoFor sourceType=openapi: path to OpenAPI YAML/JSON file
sourceTypeYesAPI source type: openapi file or explicit endpoint details
contentTypeNoFor sourceType=endpoint: Content-Type header
serverIndexNoFor sourceType=openapi: 1-based server index
testProfileNoDeterministic profile: custom, smoke, baseline, load, spike, stress, or soakcustom
endpointIndexNoFor sourceType=openapi: 1-based endpoint index
expectedStatusNoExpected response code assertion, e.g. 200
durationSecondsNoDuration for scheduled profiles such as soak. For deterministic profiles, omit or match the policy value.
allowAggressiveLoadNoRequired for aggressive profiles or requests that exceed discovered rate limits.
addResponseCodeAssertionNoFor sourceType=openapi: add a response-code assertion from the success response

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 only states the creation action and source type options, with no mention of side effects such as writing the .jmx file, whether existing files are overwritten, or whether external files are read. This is minimal for a creation tool.

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 description is a single concise sentence with no filler. It front-loads the primary action and resource. However, given the tool's 21 parameters and sibling overlap, slightly more structured guidance would be warranted without becoming verbose.

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?

This is a complex tool with 21 parameters, two distinct source modes, and overlapping siblings, yet the description provides almost no context beyond the basic action. The rich input schema compensates for parameter details but not for missing guidance about mode-specific behavior, test profiles, or when this tool is the right choice.

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%, and all 21 parameters already have meaningful descriptions and enums. The description adds no additional parameter semantics beyond restating the sourceType values already present in the schema, so the baseline score of 3 is appropriate.

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 states a specific action ('Create a JMeter test plan') and identifies the input source types ('openapi, endpoint'). However, it does not explicitly distinguish this tool from the sibling 'create_test_plan_from_openapi', so the differentiation is only implicit.

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?

There is no guidance on when to use this tool versus alternatives like create_test_plan_from_openapi or create_test_plan. The description mentions supported sourceType values but does not explain when each mode is appropriate or when a sibling should be preferred.

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

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/IAnjaniKr/jmeter-mcp-server'

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