testit-mcp-server

set_configuration

Idempotent

Partially update a configuration with JSON Patch semantics, changing only the fields you provide and leaving all other settings unchanged.

Instructions

Partially update a configuration: only the given fields change (JSON Patch). Prefer this over update_configuration.

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": "set_configuration"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Configuration UUID.
`name`	No
`isDefault`	No
`parameters`	No	Replaces the whole parameters map.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: that omitted fields are untouched and that the change set is applied as a JSON Patch. It does not mention side effects such as whether setting isDefault affects other configurations.

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?

Two tight sentences with the core semantics front-loaded and the routing advice second. No filler, no restatement of the tool name.

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?

With five parameters, a nested parameters object, and no output schema, the description covers the patch model and the sibling choice but leaves gaps around isDefault side effects and error/failure behavior. Adequate to invoke correctly in the common case, not complete for a mutation tool.

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 coverage is only 40%, so the description must compensate, and it does partially by clarifying that unspecified fields remain unchanged, which gives meaning to name, isDefault and description. However, isDefault semantics (whether it clears the previous default) and the id requirement are not elaborated, and the parameters map replacement is only documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Partially update a configuration") and immediately defines the partial-update semantics via JSON Patch. It also explicitly distinguishes itself from the sibling update_configuration, so an agent can choose between the two without opening either schema.

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

Usage Guidelines4/5

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

"Prefer this over update_configuration" gives an explicit alternative and a selection preference, which is more than most definitions offer. It stops short of stating when the alternative would be correct (e.g., full replacement) or any prerequisites such as permissions on the configuration.

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

Deploy Server