mcp-creatio

Create a system setting

create-sys-setting

Create a new system setting definition with its code, name, and value type, and optionally assign an initial value for immediate use in Creatio.

Instructions

Create a new system setting (its definition) and optionally set its first value. Value types and lookup settings: get-guide: sys-settings-guide.

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": {
      "definition": "<definition>"
    },
    "name": "create-sys-setting"
  }
}

Input Schema

Name	Required	Description	Default
`definition`	Yes
`initialValue`	No	Value to set right after creating the setting.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.8.0Oct 25, 2026

changedInput schema / properties / definition / properties / code / description

Previous value: -"Unique system setting code (e.g., \"TestSetting\"). Must follow Creatio naming rules."New value: +"Unique setting code (e.g. \"UsrMaxRetries\")."

removedInput schema / properties / definition / properties / dataValueType / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / definition / properties / dataValueType / type
```
Added value: +[
+  "string",
+  "number"
+]
```

changedInput schema / properties / definition / properties / id / description

Previous value: -"Optional GUID for the sys setting record. Auto-generated when omitted."New value: +"Id for the new setting; generated when omitted."

changedInput schema / properties / definition / properties / name / description

Previous value: -"Display name rendered in Creatio UI (e.g., \"Test setting\")."New value: +"Name shown in the Creatio UI."

changedInput schema / properties / definition / properties / referenceSchemaUId / description

Previous value: -"EntitySchema UId for lookup system settings. Required only when valueTypeName=\"Lookup\". See /sys-settings-guide prompt for the recommended VwWorkspaceObjects query to retrieve this UId."New value: +"Entity schema UId the lookup points to; required only when valueTypeName is \"Lookup\" (how to find it: get-guide: sys-settings-guide)."

changedInput schema / properties / definition / properties / valueTypeName / description

Previous value: -"Creatio data value type name. See /sys-settings-guide prompt for the table of supported valueTypeName values (Binary, Boolean, DateTime, etc.) and always send the raw value string."New value: +"Value type name (Text, Boolean, Integer, Lookup, DateTime, …) — the full list is in get-guide: sys-settings-guide."

changedInput schema / properties / initialValue / description

Previous value: -"Optional initial value to write immediately after creating the system setting."New value: +"Value to set right after creating the setting."

First observedv0.6.5Jun 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, non-destructive write operation. The description adds useful context that the setting definition is created first and the value is optional, but it does not explain duplicate-code behavior, permissions, or failure modes beyond the guide reference.

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?

Two sentences, front-loaded with the core action and followed by the optional-value behavior and guide pointer. It is efficient and has little waste, though the guide reference is a dependency rather than an explanation.

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 non-idempotent creation tool with a nested definition object and no output schema, the description is somewhat sparse. Annotations and schema cover safety and most field details, and the guide pointer helps, but return behavior and creation edge cases are not addressed.

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 50% and the definition is a nested object with many fields. The description clarifies the overall shape—definition is primary and initialValue is optional—and points to the guide for value types and lookups, but it delegates most parameter meaning to the schema and guide rather than adding independent semantic detail.

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 uses a specific verb+resource, 'Create a new system setting (its definition)', and clarifies it can optionally set the first value. It is distinguishable from siblings like set-sys-settings-value and update-sys-setting-definition, though it does not name those alternatives 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?

It implies when to use the tool by describing creation of a definition with an optional first value. However, it does not explicitly state when to choose this over set-sys-settings-value or update-sys-setting-definition, nor does it give conditions or exclusions.

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