Skip to main content
Glama

update_ip_pool

Idempotent

Modify an existing IP pool's name, ranges, comment, or next-pool reference on a MikroTik device. Use it to rename pools or adjust address allocations without creating a new pool.

Instructions

Updates an existing IP pool's name, ranges, or next-pool reference.

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" Pass "" for next_pool to clear it.

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>"
    },
    "name": "update_ip_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo
rangesNo
commentNo
new_nameNo
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

B3/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real value with the clearing rule ("Pass \"\" for next_pool to clear it"). However, it never states what a null/omitted value does for the other fields — whether omission preserves the current value or blanks it — which is the single most consequential behavior for a non-destructive update tool.

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?

One front-loaded sentence establishes the action, followed by two tight indented notes with concrete examples. The examples are load-bearing rather than padding, and nothing is repeated.

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 explained, and the annotations cover side-effect profile. Still, for a 6-parameter mutation tool with zero schema descriptions, the definition omits the null-vs-omitted semantics and the name/new_name relationship, so an agent could invoke it correctly-shaped but semantically wrong.

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%, so the description must carry parameter meaning, and it only covers two of six parameters: the hyphen/comma range format and the empty-string clearing convention for next_pool. It says nothing about `device`, `comment`, or — critically — `new_name`, leaving the agent unable to tell whether renaming requires `name` plus `new_name` or just `name`.

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?

"Updates an existing IP pool's name, ranges, or next-pool reference" gives a specific verb plus the mutable resources, so the agent knows this is a rename/edit operation on a RouterOS IP pool. It does not distinguish itself from siblings such as create_ip_pool or expand_ip_pool, and the phrase "updates ... name" blurs whether `name` is the identifier or the new value.

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?

The word "existing" weakly implies the pool must already be created, but there is no explicit when-to-use statement, no prerequisite (create the pool first with create_ip_pool), and no exclusion telling the agent to use expand_ip_pool or remove_ip_pool instead. An agent must infer routing from sibling names 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