Skip to main content
Glama

set_user_ssh_keys

Configures SSH keys for a specified MikroTik user to enable key-based authentication and reduce reliance on password-only logins.

Instructions

Sets SSH keys for a specific 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": {
      "username": "<username>",
      "key_file": "<key_file>"
    },
    "name": "set_user_ssh_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
key_fileYes
usernameYes

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.6/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, openWorld=false, idempotent=false), so the description did not need to restate it. What it fails to add is the behavior that matters for a key-install operation: whether existing keys are replaced or appended, whether the change is reversible, and what permissions are required. There is also a noticeable tension between the verb "Set" (conventionally idempotent) and idempotentHint=false, which the description never clarifies.

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?

A single grammatical sentence that is front-loaded and free of padding, so it reads cleanly. Its brevity, however, comes at the cost of substance rather than being efficient compression of real information.

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 no explanation. But for a mutating, non-idempotent tool with an ambiguous key_file argument and zero schema documentation, the description omits the operational details an agent needs to call it correctly and predict its effect.

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 description coverage is 0% for three parameters. The phrase "for a specific user" loosely maps to username, but the most ambiguous parameter, key_file, is left undefined — it is unclear whether it is a local filesystem path, a key blob, or a key type. The optional device parameter is likewise unexplained.

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 and resource: "Sets SSH keys for a specific user." An agent can tell this mutates a user's SSH keys rather than listing or removing them. It does not name the siblings (list_user_ssh_keys, remove_user_ssh_key) to draw the boundary explicitly, so it stops short of a 5.

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 prerequisites, and no mention of the related list/remove key tools as alternatives. The agent must infer that this is the right tool whenever key material needs to be installed on a user.

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