Skip to main content
Glama

remove_ipv6_address

DestructiveIdempotent

Deletes a specified IPv6 address from a MikroTik device by internal ID, print position, or address value.

Instructions

Removes an IPv6 address from the MikroTik device by ID or address value.

Notes: address_id: a RouterOS internal id (e.g. "*1"), print position ("0"), or the address value (e.g. "2001:db8::1/64").

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_id": "<address_id>"
    },
    "name": "remove_ipv6_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
address_idYes

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 destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds the practical detail of what address_id accepts, but says nothing about failure behavior when the address does not exist, whether deletion is reversible, or required permissions — meaningful gaps for a destructive call.

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 operation is front-loaded in the first sentence and the note adds only relevant detail about id format. Slightly wasteful formatting, but no filler sentences.

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

Completeness5/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 annotations cover the destructive/idempotent profile. For a two-parameter deletion tool the description supplies the one genuinely ambiguous input (address_id) and nothing essential is missing beyond optional `device` semantics.

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 coverage is 0%, so the description carries the burden, and it does explain address_id well with three concrete forms and an example. However, the second parameter `device` is never mentioned at all — its default null and how a target device is chosen remain 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?

States a specific verb and resource ("Removes an IPv6 address from the MikroTik device") plus the two accepted addressing forms, which cleanly separates it from the IPv4 sibling remove_ip_address and the list_/get_ siblings. It stops short of naming an alternative tool, but the operation itself is unambiguous.

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 versus alternatives such as remove_ip_address or how to obtain a valid address_id (e.g. via list_ipv6_addresses). The agent must infer that this is a deletion path and that the target must already exist.

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