Skip to main content
Glama

remove_ip_address

DestructiveIdempotent

Removes an IP address from a MikroTik device by ID or address value so you can clean up unused or incorrect address entries.

Instructions

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

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_ip_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

C2.7/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds no behavior beyond that: it does not say the removal is permanent, whether a confirmation or dry run exists, or what happens when the address is not found. With annotations carrying the load, this is a minimal contribution.

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?

A single efficient sentence with the action front-loaded and no filler. It is appropriately short, though it spends its few words on a scope hint while omitting the more consequential parameter 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?

For a destructive mutation the description is thin: output schema covers return values, but there is no disclosure of irreversibility, required permissions, error behavior, or how the device parameter affects targeting. An agent could invoke it but lacks the context needed to do so safely.

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 two parameters, so the description must compensate and largely fails to. It hints that address_id accepts an ID or a raw address value, which is useful, but the optional 'device' parameter (default null) is never mentioned, leaving the agent unsure which device is targeted when omitted.

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 ('Removes') and resource ('IP address') and names the target system (MikroTik device), so the agent can distinguish it from add_ip_address or get_ip_address. It does not explicitly differentiate itself from close siblings like remove_ipv6_address or remove_ip_pool, but the name plus description make the scope 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 when-to-use guidance, no mention of prerequisites (e.g., confirming the entry exists), and no reference to alternatives such as remove_ipv6_address when the address is IPv6. The agent must infer the usage context entirely.

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