Skip to main content
Glama

Manage IP Address

manage_ip_address
DestructiveIdempotent

Add, update, or remove IP addresses on MikroTik router interfaces with idempotency checks and dry-run mode.

Instructions

Add, update, or remove an IP address on a MikroTik router interface. Performs idempotency checks for add operations and supports dry-run mode for all actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routerIdNoRouter ID; omit to use the default router.
actionYesAction to perform: add, update, or remove an IP address
addressYesIP address with optional prefix length in CIDR notation (e.g., 192.168.1.1/24). Defaults to /32 if prefix is omitted.
interfaceYesInterface to assign the IP address to
networkNoNetwork address (auto-calculated from address if omitted)
commentNoOptional comment for the IP address entry
disabledNoWhether the IP address should be disabled
dryRunNoIf true, validate and return planned changes without applying
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.
Behavior4/5

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

Annotations indicate destructive and idempotent hints. The description adds specifics: idempotency for add operations, dry-run mode, and the need for a confirmation token for destructive actions. This goes beyond annotations by detailing the expected behavior.

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

Conciseness5/5

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

Two concise sentences: first states the core purpose, second adds key behaviors (idempotency, dry-run). No redundant words; every sentence provides value. Ideals for front-loading.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters, no output schema, and decent annotations, the description covers idempotency, dry-run, and confirmation token. It could explain return values or side effects more, but given the annotations and schema richness, it is fairly complete.

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 100%, so the description adds no new parameter information. It does conceptually link parameters like dryRun and confirmationToken to the behavior mentioned, but does not elaborate on their meaning beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool adds, updates, or removes an IP address on a MikroTik router interface. It specifies a concrete action and resource, and the title 'Manage IP Address' aligns perfectly. Among many manage_ siblings, this is distinct for IP address management.

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?

The description mentions idempotency checks and dry-run mode but does not explicitly guide when to use this tool over alternatives. It implicitly contrasts with other manage_ tools by focusing on IP addresses, but lacks explicit use-case conditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AliKarami/MikroMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server