testit-mcp-server

create_configuration_parameter

Creates a configuration parameter with a defined set of allowed values for TestIT projects, enabling consistent test configuration.

Instructions

Create a configuration parameter with allowed values.

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": {
      "name": "<name>",
      "values": "<values>"
    },
    "name": "create_configuration_parameter"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Parameter name, e.g. browser.
`values`	Yes	Allowed values, e.g. ["firefox", "chrome"].
`projectId`	No
`projectIds`	No	Projects the parameter is available in (default: current project).
`projectName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so safety is largely covered. The description adds nothing beyond them — notably it does not say what happens when the name already exists (relevant given idempotentHint=false), nor whether values can be extended later.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, but the brevity comes at the cost of information rather than through tight editing of rich content.

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 a 5-parameter mutation tool with no output schema and partial parameter coverage, the definition says nothing about the project scoping options, duplicate-name behavior, or what is returned. An agent could call it, but would be guessing at several semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 60%, and the two undocumented properties (projectId, projectName) sit alongside projectIds with no explanation of how they relate or which takes precedence. The description only echoes "allowed values", which the schema already states in the values field.

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?

States a specific verb and resource ("Create a configuration parameter") plus the key constraint ("allowed values"), so it is distinguishable from delete_/get_/update_configuration_parameter. It does not distinguish itself from create_configuration, which creates the container rather than a parameter.

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 when-to-use or when-not-to-use guidance, and no mention of prerequisites such as an existing configuration. The create-vs-update decision and the alternative of adding a value to an existing parameter are left entirely to inference.

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

Deploy Server