testit-mcp-server

update_configuration_parameter

DestructiveIdempotent

Replace a configuration parameter in TestIT with its full set of values and projects, removing any values not included.

Instructions

Replace a configuration parameter (PUT): name, the FULL list of values and projects. Values not sent are removed.

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

Input Schema

Name	Required	Description
`id`	Yes	Configuration parameter UUID.
`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

A3.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond them by spelling out the exact destructive mechanism: data omitted from values/projects is removed, not preserved. It stops short of describing the response or permission requirements.

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?

A single front-loaded sentence with the destructive warning in the final clause; no filler, and the most consequential fact is not buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 6-parameter mutation with no output schema, the description covers the core mechanics but omits what scoping (current project vs projectIds) means in practice and what the call returns or affects downstream. Adequate minimum, with noticeable gaps.

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

Parameters4/5

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

Schema coverage is 67%, leaving projectId and projectName undescribed. The description compensates by framing the three meaningful inputs and stressing that values must be the complete list, which is the single most important semantic for correct invocation.

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 ('Replace a configuration parameter (PUT)') and clarifies the replacement covers name, values, and projects. It is clearly distinct from create/delete/get siblings by the verb, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'FULL list ... Values not sent are removed' phrasing implicitly tells the agent this is a full-replacement call and must supply complete data. It does not state when to prefer it over a partial-update path or mention any prerequisite/permission context, so usage is only implied.

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

Deploy Server