iSuite Operations MCP Server

update_config_value

Update an iSuite configuration value using dot-notation key and new value. Records the change reason in the audit log and optionally triggers a service restart.

Instructions

Update a specific iSuite configuration value. Requires appropriate admin permissions.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "update_config_value"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Dot-notation config key to update.
`value`	Yes	New value to set. Type must match the key's expected type.
`reason`	No	Reason for the change (recorded in audit log).
`restartRequired`	No	Whether this change requires a service restart to take effect.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses mutation and admin permission requirement, but omits critical behaviors: whether changes are audited (despite 'reason' parameter), what happens if the key doesn't exist, type validation details, or if restartRequired is enforced. The description is insufficient for safe invocation.

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 sentence with no redundancy, achieving high conciseness. However, it sacrifices completeness by omitting key behavioral details. It earns a 4 for efficiency but loses a point for being overly terse.

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?

Given the tool's complexity (mutation, audit, restart implications) and no output schema, the description is too brief. It fails to explain return values, error states, or when restart is needed. More context is necessary for an agent to use this tool correctly.

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 100%, so the baseline is 3. The description adds no extra meaning beyond what the parameter descriptions already provide (e.g., dot-notation format, expected type matching, audit reason). It does not improve understanding of parameter usage.

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 states the action ('Update') and the resource ('specific iSuite configuration value'), which distinguishes it from read-only or listing tools like get_config_value and list_config_keys. However, it does not explicitly clarify whether the key must already exist or if it can create new entries.

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 only mentions a prerequisite ('Requires appropriate admin permissions') but provides no guidance on when to use this tool versus alternatives like compare_configs or validate_config. It lacks context for preferred scenarios or exclusions.

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