Skip to main content
Glama
configcat

ConfigCat MCP Server

Official

replace-setting-value

Replace the complete value, rollout rules, and percentage rules of a feature flag setting in a given environment. Omitting an attribute resets it.

Instructions

This endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment.

Only the value, rolloutRules and percentageRules attributes are modifiable by this endpoint.

Important: As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset.

For example: We have the following resource.

{
  "rolloutPercentageItems": [
    {
      "percentage": 30,
      "value": true
    },
    {
      "percentage": 70,
      "value": false
    }
  ],
  "rolloutRules": [],
  "value": false
}

If we send a replace request body as below:

{
  "value": true
}

Then besides that the default value is set to true, all the Percentage Rules are deleted. So we get a response like this:

{
  "rolloutPercentageItems": [],
  "rolloutRules": [],
  "value": true
}

The rolloutRules property describes two types of rules:

  • Targeting rules: When you want to add or update a targeting rule, the comparator, comparisonAttribute, and comparisonValue members are required.

  • Segment rules: When you want to add add or update a segment rule, the segmentId which identifies the desired segment and the segmentComparator members are required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentIdYesThe identifier of the Environment.
settingIdYesThe id of the Setting.
reasonNoThe reason note for the Audit Log if the Product's "Config changes require a reason" preference is turned on.
requestBodyYes
Behavior5/5

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

With no annotations provided, the description fully discloses the destructive nature (complete replace, resets attributes not listed). It provides a concrete example illustrating the behavior, making the tool's actions transparent.

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 lengthy due to examples and detailed rule explanations, but it's well-structured with sections and clear headings. Given the complexity of the tool, the length is justified, though some sentences could be trimmed.

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

Completeness4/5

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

The description is fairly complete for a complex tool with no output schema. It explains the replace behavior, modifiable attributes, rule types, and includes an example. However, it does not mention the response format, which could be inferred but is not explicit.

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?

The input schema covers 75% of parameters with descriptions. The description adds meaning beyond the schema by explaining the modifiable attributes (value, rolloutRules, percentageRules) and detailing the two types of rules with required fields, thus providing extra context.

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?

The description clearly states the tool replaces the whole value of a Feature Flag or Setting in a specified Environment. It lists modifiable attributes and provides examples, distinguishing it from sibling tools like replace-setting-value-v2 or update-setting-value.

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?

The description explains the complete replace behavior and warns about resetting attributes not included. It also describes the two rule types with required members. However, it lacks explicit guidance on when to use this vs. other related tools like replace-setting-value-v2.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/configcat/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server