Skip to main content
Glama
Sign In
mguttmann

action1-mcp-server

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update user

action1_update_user
Destructive

Update an existing user's profile, contact details, timezone, enabled status, or credentials by user ID, with preview by default and explicit confirmation required to execute.

Instructions

Update user. Updates an existing user. Perm: manage_users.

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body
confirmNoRequired to execute. Exact string "YES".
dry_runNoDefault true (preview). Set false to execute.
user_idYesProvide a specific user ID.

Output Schema

NameRequiredDescriptionDefault
toolNo
valueNo
dry_runNo
would_sendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.6.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / body / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / body / anyOf
      Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "enabled": {
+        "description": "Defines if the user is enabled or disabled.",
+        "enum": [
+          "yes",
+          "no"
+        ],
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "last_name": {
+        "type": "string"
+      },
+      "phone": {
+        "type": "string"
+      },
+      "session_timeout": {
+        "description": "The session timeout in seconds for API and GUI.",
+        "type": "number"
+      },
+      "timezone": {
+        "description": "Timezone identifier.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "enabled": {
+        "description": "Defines if the user is enabled or disabled.",
+        "enum": [
+          "yes",
+          "no"
+        ],
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "password": {
+        "description": "When creating API credentials, the Enterprise Admin can read the password.",
+        "type": "string"
+      },
+      "timezone": {
+        "description": "Timezone identifier.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • changedInput schema / properties / body / description
      Previous value: -"Request body (schema: object)"New value: +"Request body"
    • removedInput schema / properties / body / type
      Removed value: -"object"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • addedOutput schema / properties / dry_run
      Added value: +{}
    • addedOutput schema / properties / tool
      Added value: +{}
    • addedOutput schema / properties / value
      Added value: +{}
    • addedOutput schema / properties / would_send
      Added value: +{}
  2. First observedv0.5.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true. The description adds a useful permission gate, but omits the most consequential behavior: that changes only execute after confirm="YES" with dry_run=false, and that fields omitted from the body may be left untouched. For a destructive mutation, that safety flow should be surfaced in prose.

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

Conciseness2/5

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

Three fragments, of which the first two say the same thing ("Update user" / "Updates an existing user"). That space would be better spent on the dry_run/confirm execution flow.

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?

An output schema exists so return values need not be explained, but for a destructive, non-idempotent user mutation the description should at least flag the two-step preview/confirm execution model and the manage_users requirement's implications. Neither is present beyond the bare permission string.

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 the schema already documents user_id, body, confirm and dry_run, including the "Default true (preview)" note. The description contributes nothing about parameters beyond the implicit permission, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update user. Updates an existing user." restates the name and title without adding scope. Nothing distinguishes it from action1_update_me or action1_update_organization, nor does it say what aspects of the user can change.

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 guidance on when to use this versus action1_create_user, action1_update_me, or action1_get_user. The only actionable cue is the permission requirement "Perm: manage_users", which hints at prerequisites but not at tool selection.

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