Skip to main content
Glama

add_ipv6_address

Assign an IPv6 address to a MikroTik interface, optionally using a prefix pool, Router Advertisement, EUI-64 host generation, or skipping Duplicate Address Detection.

Instructions

Adds an IPv6 address to an interface on the MikroTik device.

Notes: address: IPv6 address with prefix length, e.g. "2001:db8::1/64" or "fe80::1/64". When from_pool is used, supply the host part only, e.g. "::1/64". advertise: include this prefix in Router Advertisements (default no). eui_64: derive the host part of the address from the interface MAC. from_pool: name of an IPv6 pool to take the prefix from. no_dad: skip Duplicate Address Detection.

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": {
      "address": "<address>",
      "interface": "<interface>"
    },
    "name": "add_ipv6_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
eui_64No
no_dadNo
addressYes
commentNo
disabledNo
advertiseNo
from_poolNo
interfaceYes

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the description needn't restate the safety profile. It adds useful behavioral context beyond that: the address string format, that `advertise` defaults to no, and what `no_dad` and `eui_64` change about how the address is formed. It omits what happens on a duplicate address, whether the change requires elevated permissions, and whether re-adding is safe.

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

Conciseness4/5

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

The one-line purpose statement is front-loaded and followed by a compact notes list, which is an efficient structure for a 9-parameter tool. The per-parameter notes are terse and earn their place; nothing is redundant with the annotations.

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

Completeness3/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 described, and the annotations cover the mutation safety profile. For a 9-parameter mutation with 0% schema coverage, though, the description should at minimum say what `disabled` and `comment` do and whether `device` defaults to a single configured router, which it does not.

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 0%, so the description carries the burden and it partially delivers: `address` format with a concrete example, plus `advertise`, `eui_64`, `from_pool`, and `no_dad` are all explained with meaning beyond the bare property names. The parameters `device`, `comment`, and `disabled` are not mentioned at all, and `interface` (required) is unexplained, leaving roughly half the surface 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 opens with a specific verb and resource: 'Adds an IPv6 address to an interface on the MikroTik device.' That is unambiguous, and the tool name plus the IPv6 qualifier implicitly separate it from add_ip_address. It does not explicitly name a sibling to disambiguate against, 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 Guidelines3/5

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

Usage context is implied by the notes (e.g. use `from_pool` to take the prefix from a pool, supply host part only in that case), which is genuine guidance on how to combine parameters. However, there is no statement of when to prefer this over alternatives such as add_ip_address or from_pool versus a literal address, and no prerequisites are given.

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