Skip to main content
Glama

ros_remove

Delete a MikroTik RouterOS item by ID, name, or key=value pair from a specified configuration path. Use it to remove addresses, rules, or other entries when you know the path and identifier.

Instructions

Remove an item by .id, name, or 'key=value' (e.g. path='/ip/address', item='address=10.0.0.1/24').

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": {
      "path": "<path>",
      "item": "<item>"
    },
    "name": "ros_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
pathYes
routerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a destructive mutation. It never says whether the removal is permanent, what happens when multiple items match the selector, whether confirmation is needed, or how the router is chosen when 'router' is omitted.

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 tight sentence with the selector syntax front-loaded and an inline example. Dense but every clause adds information; no filler.

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, no-annotation, no-output-schema tool with 0% schema coverage and three parameters, the description is thin: it omits the router target, safety/irreversibility, multi-match behavior, and any return information.

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 0%, so the description must compensate. It does add real meaning for 'item' (three selector forms plus an example) and illustrates 'path' via '/ip/address', but the 'router' parameter is never mentioned and the path format is only inferable from the example.

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 ('Remove') and resource ('an item'), and names the three accepted identifier forms (.id, name, 'key=value') with a concrete RouterOS example. It is clearly distinguishable from ros_add/ros_set/ros_print by the verb, though it never explicitly contrasts with those siblings.

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 statement of when to use this versus ros_set, ros_disable, or ros_command, and no prerequisites (connected router, target selection). Usage is only implied by the verb 'Remove'.

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