Skip to main content
Glama

Правка своего профиля

update_user_profile
Destructive

Правка своего профиля: имя, язык интерфейса, часовой пояс, оформление и подписки на письма. Часовой пояс важен отдельно — от него зависят все даты в отчётах и выгрузках. Передавайте только те поля, которые нужно поменять; подписки можно менять по одной, остальные останутся как были. Смена почты и пароля здесь недоступна (там код из письма и текущий пароль), аватар тоже — это загрузка картинки. Прочитать профиль — user://me.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoЯзык интерфейса и писем: ru, en, es и другие коды.
nameNoИмя, от 3 до 60 символов, без ссылок. У владельца аккаунта им же называются его аккаунты.
themeNoОформление кабинета: light, dark или auto.
timezoneNoЧасовой пояс в виде Europe/Moscow. От него зависят даты в отчётах и выгрузках.
subscribe_actionNoПисьма о действиях в аккаунте.
subscribe_billingNoПисьма об оплате и списаниях.
subscribe_marketingNoПисьма с новостями и предложениями.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Имя, от 3 до 255 символов. У владельца аккаунта им же называются его аккаунты."New value: +"Имя, от 3 до 60 символов, без ссылок. У владельца аккаунта им же называются его аккаунты."
    • changedInput schema / properties / name / maxLength
      Previous value: -255New value: +60
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the supplied annotations by describing partial-merge semantics (unmentioned fields remain unchanged) and the downstream consequence of one field ('от него зависят все даты в отчётах и выгрузках'), which matters for a mutation tool. It does not discuss error/validation behavior or what a successful call returns. Note a mild tension with the destructiveHint=true annotation, but the description's clarification of merge semantics is consistent with MCP's definition of a destructive update rather than a contradiction.

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?

Front-loads the field list, then moves to the important caveat (timezone), then partial-update rules, then exclusions. Dense but every clause carries information. The final sentence bundles three separate exclusions, which is slightly compressed but still readable.

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 mutation tool with no output schema, it covers scope, partial-update behavior, exclusions, and the read alternative — enough to call correctly. It leaves the agent without any statement about the response or validation failures, which is the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by adding cross-parameter meaning the schema lacks — that all fields are optional and only supplied ones are applied, and that the three subscribe_* flags are independently settable. The timezone and name notes largely restate the schema descriptions rather than adding format detail.

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?

Opens with a specific verb+resource ('Правка своего профиля') and immediately enumerates exactly which fields are in scope (имя, язык, часовой пояс, оформление, подписки). It also carves out what this tool is not — смена почты/пароля и аватар — so an agent can distinguish it from sibling tools like get_user_me or manage_user_sessions without opening the schema.

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?

Gives explicit operating instructions: 'Передавайте только те поля, которые нужно поменять', subscriptions can be toggled one at a time without disturbing others, and it names the alternative path for excluded operations (email/password require a code and current password, avatar is an image upload). It also routes reads to 'user://me', which is a clear when-not-to-use signal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources