Skip to main content
Glama

create_ip_pool

Create an IP pool on a MikroTik device by specifying a name and one or more address ranges, enabling DHCP and firewall rules to allocate addresses from defined ranges.

Instructions

Creates an IP pool with the given address ranges on the MikroTik device.

Notes: ranges: hyphen-separated range(s) e.g. "192.168.1.1-192.168.1.100" Multiple ranges comma-separated: "10.0.0.1-10.0.0.50,10.0.0.100-10.0.0.120"

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": {
      "name": "<name>",
      "ranges": "<ranges>"
    },
    "name": "create_ip_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo
rangesYes
commentNo
next_poolNo

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.9/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 mutation safety profile is covered. The description adds value by giving concrete range syntax, but says nothing about what happens on a duplicate pool name, how the optional 'device' target is resolved when null, or any error behavior — reasonable gaps against the annotation baseline, but still gaps.

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 core action is front-loaded in a single sentence, and the notes block is short and scannable with examples. Slightly awkward formatting in the notes (inconsistent indentation, trailing blank line) keeps it from being exemplary.

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 not be described, and annotations cover the safety traits. But for a 5-parameter mutation tool with zero schema documentation, the definition leaves device targeting, next_pool semantics, and duplicate-name behavior unexplained, which is not enough for confident invocation.

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% across 5 parameters, so the description carries the full burden, and it only explains 'ranges' (hyphen and comma syntax). The other four — name, device, comment, next_pool — receive no meaning at all, including next_pool, whose semantics (chained pool fallback) are non-obvious.

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 states a specific verb and resource ('Creates an IP pool') plus the key payload ('with the given address ranges') and the target ('on the MikroTik device'). It is unambiguous on its own, but never distinguishes itself from siblings such as update_ip_pool or create_dhcp_pool, so it stops short of 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 explicit when-to-use or when-not-to-use guidance, no mention of the alternative tools (update_ip_pool for existing pools, get_ip_pool/list_ip_pools for reads), and no stated prerequisites such as name uniqueness or which device the pool is created on. The agent must infer all routing decisions from the name alone.

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