Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

cases_save

Create or modify an operations case: supply a case ID to change its name, description, icon, theme, settings, or archive status; omit it to create one and receive all standard roles.

Instructions

Без указания дела создаёт новое (вы становитесь владельцем, разворачиваются пять ролей: владелец, администратор, конструктор, оператор, наблюдатель). С указанием — меняет название, описание, знак и оформление или убирает дело в архив.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoКакое дело менять. Не указывайте, чтобы создать новое.
nameNoНазвание дела.
emojiNoЗнак дела, например 🛍. По умолчанию ◆.
accentNoОформление: platinum, signal, aurora, ultra, ember, moss, rose.
archivedNoУбрать дело в архив или вернуть из него. Только при изменении.
settingsNoНастройки дела: карта целиком.
descriptionNoОписание; null — очистить.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • addedInput schema / properties / description / anyOf
      Added value: +[
+  {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"Описание."New value: +"Описание; null — очистить."
    • removedInput schema / properties / description / maxLength
      Removed value: -2000
    • removedInput schema / properties / description / type
      Removed value: -"string"
    • addedInput schema / properties / settings
      Added value: +{
+  "additionalProperties": {},
+  "description": "Настройки дела: карта целиком.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent write tool. The description adds meaningful side-effect detail: creating a case makes the caller owner and deploys five roles, while updating can change fields or archive the case.

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 compact sentences with no wasted wording. The create case is front-loaded, followed immediately by the update/archive case.

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?

For a 7-parameter save tool with no required parameters and no output schema, the description covers the main create/update split and key side effects. It omits the nested 'settings' parameter and the unarchive behavior that the schema mentions.

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 each parameter is already documented. The description synthesizes the role of the 'case' parameter and lists some editable fields, but adds little beyond what the schema already states.

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 states a specific create-or-update purpose and clearly explains the two modes controlled by the 'case' parameter. It does not, however, explicitly differentiate itself from sibling case tools such as cases_get, cases_list, or cases_delete.

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?

It gives clear context for both modes: omit 'case' to create a new case, provide it to modify an existing one. It does not mention when to avoid this tool or name alternative case-management tools.

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