Skip to main content
Glama

update_user

Idempotent

Modify an existing MikroTik RouterOS user account: change its group, address, password, comment, disabled state, or rename it. Use it to update access settings for a specified user.

Instructions

Updates a user.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
groupNo
deviceNo
addressNo
commentNo
disabledNo
new_nameNo
passwordNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=false, which covers the safety profile. The description adds nothing beyond that — no note on which fields are mutable, whether omitted fields are left untouched (versus cleared to null defaults), or what privileges are needed for password or group changes.

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 words with no filler, but this is under-specification rather than conciseness. Nothing is front-loaded because there is essentially no content to structure.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 8 undocumented parameters, an output schema, and rename/password operations among them, a three-word description is far from adequate. The output schema reduces the need to explain returns, but the input-side guidance is entirely absent.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, so the description carries the full burden and provides nothing. Critically, parameters default to null but the semantics of null (leave unchanged vs. clear the field) are undocumented, and the distinction between name and new_name is unexplained.

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?

"Updates a user" restates the tool name and title verbatim, giving no scope beyond the obvious verb+resource. It does not distinguish the tool from siblings like add_user, remove_user, or disable_user, nor say what aspects of a user are updatable.

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?

There is no when-to-use guidance, no mention of alternatives such as disable_user for toggling state or update_user_group for group changes, and no prerequisites. The only inference available is the bare name.

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