Skip to main content
Glama

user_updateProfile

Update an existing Operaton user's first name, last name, or email to keep profile details current; returns confirmation on success.

Instructions

Update the profile of an existing Operaton user: firstName, lastName, or email. Returns confirmation on success.

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": {
      "id": "<id>"
    },
    "name": "user_updateProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It notes a success confirmation, but says nothing about required permissions, whether the update is partial or a full replace, what happens to fields not supplied, or whether the change is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the outcome stated up front, so there is no padding. However, brevity here comes at the cost of accuracy, since half the text describes payload fields the schema does not accept.

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

Completeness2/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 annotations, no output schema, and a schema that omits every field the description mentions, the definition leaves the agent unable to construct a correct call. It needs to reconcile the mentioned fields with the id-only schema and cover permissions or replace semantics.

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

Parameters2/5

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

Schema coverage is 0% for the single parameter, and the description never explains that the sole schema parameter is the user id. Worse, the fields it does enumerate (firstName, lastName, email) do not exist anywhere in the input schema, so the description actively misdirects an agent about what it can send.

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?

States a specific verb+resource ("Update the profile of an existing Operaton user") and enumerates the mutable fields, which is clearer than the name alone. It does not differentiate from nearby siblings such as user_updatePassword or user_getProfile, but the intent is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no pointer to the sibling that should be used for reading a profile (user_getProfile) or changing credentials (user_updatePassword). The only implied constraint is that the user must already exist.

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