action1-mcp-server

Create a new setting

action1_create_setting

Destructive

Configure system settings by creating a new entry. Specify the setting value and template ID, then select the deployment scope (Enterprise, Organization, or Group) to apply the changes.

Instructions

Create a new setting. Creates a new setting. At this time, all setting templates are enterprise-wide. Perm: manage_advanced_settings.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: SettingPayloadPost)
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`scope`	No
`value`	No
`dry_run`	No
`value_type`	No
`would_send`	No
`description`	No
`template_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / body / properties

Added value: +{
+  "scope": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "object": {
+          "description": "Select specific organization, group, or apply everywhere. Accepts: all, {orgId}, {groupId}.",
+          "type": "string"
+        },
+        "type": {
+          "description": "The scope to apply the setting to.",
+          "enum": [
+            "Enterprise",
+            "Organization",
+            "Group"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "object"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "template_id": {
+    "description": "The ID of the template.",
+    "type": "string"
+  },
+  "value": {
+    "description": "The value defined for this setting.",
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "value",
+  "scope",
+  "template_id"
+]

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
addedOutput schema / properties / description
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / name
```
Added value: +{}
```
addedOutput schema / properties / scope
```
Added value: +{}
```
addedOutput schema / properties / self
```
Added value: +{}
```
addedOutput schema / properties / template_id
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / type
```
Added value: +{}
```
addedOutput schema / properties / value
```
Added value: +{}
```
addedOutput schema / properties / value_type
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose destructiveHint=true, openWorldHint=true, non-idempotent behavior, and readOnlyHint=false. The description adds useful context about the required permission and enterprise-wide template scope, but it does not mention the dry_run/confirm safety flow documented in the schema. There is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but the first two sentences are exact duplicates: 'Create a new setting. Creates a new setting.' That redundancy does not earn its place and makes the structure slightly wasteful.

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 definition provides sufficient context for a create mutation: purpose, permission requirement, and enterprise-wide template scope. The schema already covers the safety controls, and an output schema exists, so the description need not explain return values. It could be stronger with explicit guidance on dry_run versus confirm execution.

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 description coverage is 100%, so the input schema already explains body, value, scope, template_id, confirm, and dry_run. The description adds no parameter-level details beyond what the schema provides, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'Create a new setting.' It also adds that setting templates are enterprise-wide, which gives scope context. It does not explicitly differentiate from update_setting, so it stops short of a 5.

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 description implies this is for creating new settings and states the required permission, manage_advanced_settings. However, it gives no explicit when-to-use guidance versus update_setting or other siblings, and no exclusion conditions.

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

Deploy Server