Skip to main content
Glama

add_user

Add a new user to a MikroTik device by specifying name, password, and optional group, address, comment, or disabled status.

Instructions

Adds a user to MikroTik device.

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>",
      "password": "<password>"
    },
    "name": "add_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
groupNoread
deviceNo
addressNo
commentNo
disabledNo
passwordYes

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

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say what happens if the user already exists (non-idempotent), what permissions or credentials are needed, or how the password is handled.

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?

It is a single front-loaded sentence with no wasted words, which is structurally clean. The brevity is under-specification rather than efficiency, so it earns adequacy but not praise.

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?

This is a mutation tool with 7 parameters, two of them required (name and password), and zero parameter documentation. An output schema exists, so return values need not be described, but the description should still cover creation semantics, duplicate handling, and the meaning of the optional fields.

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 7 parameters, so the description carries the full burden of explaining them, and it explains none. Key semantics such as the meaning of 'group' (defaulting to 'read'), 'address' (source-IP restriction), 'device' (target router when null), and 'disabled' are left entirely undocumented.

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?

The description states a specific verb and resource: it adds a user to a MikroTik device. That much is unambiguous. However, it gives no differentiation from closely related siblings such as update_user, get_user, or add_user_group, so an agent must infer which user-mutation tool applies.

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 guidance on when to use this tool instead of update_user, add_user_group, or enable_user/disable_user. No prerequisites are stated, such as whether the target user must not already exist or whether the device parameter is required when multiple devices are configured.

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