Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Изменить данные аккаунта

account_update

Update profile fields such as full name, birth date, phone, timezone and Telegram/MAX IDs. Send only fields to change; missing name and birth date leaves API access locked.

Instructions

Меняет ФИО, дату рождения, телефон, часовой пояс и номера в Telegram и MAX учётной записи — по номерам бот шлёт участнику весточки из сценария (узел «Сообщить в чат» с адресатом «участник команды»). Передавайте только те поля, которые нужно изменить: остальные останутся как есть. Этим же инструментом проходят шаг знакомства: пока фамилии, имени и даты рождения нет, API закрыт целиком.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phoneNoТелефон.
max_idNoНомер человека в MAX. null — стереть.
timezoneNoЧасовой пояс, например Europe/Moscow.
last_nameNoФамилия.
avatar_urlNoАдрес аватара; null — удалить.
birth_dateNoДата рождения в виде ГГГГ-ММ-ДД. Без неё профиль считается незаполненным.
first_nameNoИмя.
middle_nameNoОтчество.
telegram_idNoНомер в Telegram (число, не @имя). null — стереть.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.2.0
    • addedInput schema / properties / avatar_url
      Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Адрес аватара; null — удалить."
+}
    • changedInput schema / properties / birth_date / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / first_name / anyOf
      Added value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / first_name / maxLength
      Removed value: -80
    • removedInput schema / properties / first_name / type
      Removed value: -"string"
    • addedInput schema / properties / last_name / anyOf
      Added value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / last_name / maxLength
      Removed value: -80
    • removedInput schema / properties / last_name / type
      Removed value: -"string"
    • addedInput schema / properties / middle_name / anyOf
      Added value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / middle_name / maxLength
      Removed value: -80
    • removedInput schema / properties / middle_name / type
      Removed value: -"string"
    • addedInput schema / properties / phone / anyOf
      Added value: +[
+  {
+    "maxLength": 32,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / phone / maxLength
      Removed value: -32
    • removedInput schema / properties / phone / type
      Removed value: -"string"
    • addedInput schema / properties / timezone / anyOf
      Added value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / timezone / maxLength
      Removed value: -64
    • removedInput schema / properties / timezone / type
      Removed value: -"string"
  2. Changed2 schema fields changedv0.1.17
    • addedInput schema / properties / max_id
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Номер человека в MAX. null — стереть."
+}
    • addedInput schema / properties / telegram_id
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Номер в Telegram (число, не @имя). null — стереть."
+}
  3. Changed1 schema field changedv0.1.14
    • addedInput schema / properties / birth_date
      Added value: +{
+  "description": "Дата рождения в виде ГГГГ-ММ-ДД. Без неё профиль считается незаполненным.",
+  "type": "string"
+}
  4. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false, openWorld=true) the description discloses two non-obvious traits: patch semantics (unspecified fields are untouched) and an onboarding gate (all name/birth-date fields required before the API otherwise works). It omits that passing null erases a value and says nothing about the response or side effects of the Telegram/MAX notification.

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?

Three sentences, front-loaded with the action and affected fields, with the two behavioral notes packed in tightly. Dense but each clause carries information; the parenthetical about the scenario node is somewhat tangential to tool selection.

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 mutation tool with no output schema and rich annotations, the definition covers mutability model and a critical precondition. Remaining gaps (null-erase behavior, response shape, side effects of outward notifications) are partly covered by the schema and are relatively minor.

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% and the schema itself documents every field, including the important null-erases semantics for max_id/telegram_id/avatar_url. The description adds only the high-level field list and the partial-update rule, so the baseline 3 is appropriate.

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?

States a specific verb (меняет) and resource (данные аккаунта) and enumerates the exact mutable fields (ФИО, дата рождения, телефон, часовой пояс, Telegram/MAX id), which clearly separates it from account_security, account_appearance and account_password.

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?

Gives concrete usage guidance: pass only the fields to change, the rest stay as-is, and it names a second use case (прохождение шага знакомства). It does not point to a sibling for the cases this tool does not cover, so it stops short of a 5.

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