Skip to main content
Glama
Sign In
jmeter-mcp-server

jmeter-mcp-server

by IAnjaniKr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run_test

Run a JMeter test plan from a .jmx file and return execution results for performance testing.

Instructions

Run a JMeter test plan and return results

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "testfile": "<testfile>"
    },
    "name": "run_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
testfileYesPath to the .jmx test file
outputdirNoOutput directory for results

Schema Changelog

Changes observed during successful MCP inspections.

  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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It notes that running a test occurs and results are returned, but does not disclose side effects, execution duration, failure behavior, output format, or resource implications beyond the schema.

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 clear sentence with no fluff or redundant content. It is efficient and front-loaded, though it could include more usage context without becoming bloated.

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 an execution tool with no annotations and no output schema, this description is incomplete. It omits details about expected results format, whether outputdir is required or optional in practice, how long execution may take, and what happens on test failure or invalid test files.

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%, so the schema already documents both parameters adequately. The description adds no additional parameter-level detail, such as how outputdir is used or what the return value contains, but it does not need to compensate much because the schema is complete.

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 identifies the action (Run), the resource (a JMeter test plan), and the outcome (return results). It is distinguishable from sibling tools like read_test_file or create_test_plan, though it does not explicitly contrast itself with them.

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 says what the tool does but does not indicate when to use it versus alternatives, nor what prerequisites or conditions apply. An agent must infer that this is meant for executing an already-created test plan.

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

Deploy Server

Other Tools