Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Создать или изменить роль

roles_save

Create or update a case role with a specific permission set. Built-in roles are read-only; use copy_of to duplicate a preset and customize the copy.

Instructions

Заводит в деле свою роль с нужным набором прав или меняет существующую. Готовые роли (владелец, администратор, конструктор, оператор, наблюдатель) правке не поддаются — укажите copy_of, чтобы сделать копию пресета и настроить её.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
nameNoНазвание роли.
roleNoКакую роль менять. Не указывайте, чтобы создать новую.
slugNoКороткое имя новой роли. После создания его сменить нельзя.
accentNoЦвет метки роли.
copy_ofNoСкопировать эту роль (обычно готовый пресет), чтобы править копию.
positionNoПорядок в списке ролей.
descriptionNoОписание роли. null — стереть.
permissionsNoНабор прав. Заменяет прежний целиком, а не дополняет его.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • addedInput schema / properties / description / anyOf
      Added value: +[
+  {
+    "maxLength": 1000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"Описание роли."New value: +"Описание роли. null — стереть."
    • removedInput schema / properties / description / maxLength
      Removed value: -1000
    • removedInput schema / properties / description / type
      Removed value: -"string"
    • changedInput schema / properties / permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "market.publish",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "request.view",
+  "request.create",
+  "request.edit",
+  "request.manage",
+  "counterparty.view",
+  "counterparty.manage",
+  "ai.view",
+  "ai.manage",
+  "extension.view",
+  "extension.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
    • addedInput schema / properties / slug
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 64,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Короткое имя новой роли. После создания его сменить нельзя."
+}
  2. Changed1 schema field changedv0.1.16
    • changedInput schema / properties / permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
  3. Changed1 schema field changedv0.1.14
    • changedInput schema / properties / permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
  4. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds meaningful behavioral context beyond those annotations: built-in presets are immutable and copy_of is the required workaround. It does not clarify side effects of changing permissions or idempotency behavior, but the annotations cover part of that burden.

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, front-loaded with the primary action, followed by the critical preset constraint and copy_of remedy. Every sentence earns its place.

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

Completeness5/5

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

For a 9-parameter mutation tool with no output schema and full schema coverage, the description covers the essential context: what it does, the preset immutability constraint, and the required copy_of workaround. Nothing critical is missing for an agent to call it 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 description coverage is 100%, so all 9 parameters are already documented in the input schema. The description reinforces the permission-set purpose and copy_of for presets, but it adds little parameter detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: it creates a custom role in a case or modifies an existing one. It also distinguishes the operation from built-in presets, which cannot be edited. An agent can select it confidently against siblings like roles_delete.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: to create a role with a desired permission set or change an existing role. It also gives an important when-not rule and alternative: built-in roles cannot be edited, so copy_of must be used to clone and customize a preset.

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

Deploy Server

Other Tools