jmeter-mcp-server

Overview Schema Source Related Servers Discussions Admin

add_csv_data_config

Add CSV Data Set Config to a JMeter .jmx file for data-driven testing, allowing you to specify CSV file, variable names, delimiter, sharing mode, and recycling options.

Instructions

Add a CSV Data Set Config for data-driven testing

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>",
      "filename": "<filename>",
      "variableNames": "<variableNames>"
    },
    "name": "add_csv_data_config"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Optional name
`recycle`	No	Recycle data at end
`filename`	Yes	Path to the CSV file
`testfile`	Yes	Path to the .jmx file
`delimiter`	No	Field delimiter	,
`stopThread`	No	Stop thread at end of file
`sharingMode`	No	How data is shared between threads	shareMode.all
`variableNames`	Yes	Comma-separated variable names (e.g., 'username,password')
`ignoreFirstLine`	No	Skip header row

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

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 behavioral burden; it only says 'Add a CSv Data Set Config for data-driven testing.' It implies mutation of a testfile but does not disclose that the .jmx file is modified in place, whether the operation is idempotent, whether the CSV file must already exist, or where the element is placed in the test plan.

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?

A single, front-loaded sentence with no filler; the verb and resource appear immediately. It is appropriately terse, though it could earn a 5 by adding a behavioral clause without bloating.

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?

With 9 parameters (3 required), no output schema, and no annotations, a one-sentence description is thin. The rich schema covers parameter meaning, but an agent gets no context on side effects (in-place .jmx modification), placement, or prerequisites, which matters for a tool that mutates a test artifact.

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 every parameter is already documented in the schema. The description adds no parameter-level meaning beyond the general 'data-driven testing' framing, which keeps this at baseline 3.

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 verb ('Add'), a specific resource ('CSV Data Set Config'), and a purpose ('data-driven testing'), so an agent can infer this adds a JMeter CSV-data element to a test artifact. It is distinguishable from sibling add_* tools by the named element type (vs. add_http_sampler, add_assertion, add_timer), though it does not explicitly contrast with them or name the target (.jmx testfile).

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?

No guidance is provided on when to use this tool vs. alternatives such as create_test_plan_from_openapi or add_http_sampler, nor when not to use it. An agent must infer from the element type that this is for setting up data-driven tests.

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

Deploy Server