Skip to main content
Glama

ros_disable

Disables a specified RouterOS item, such as an interface, firewall rule, or route, by path and item name to stop it from running.

Instructions

Disable an item (interface, rule, route ...).

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_disable"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
pathYes
routerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never says whether the disabled state persists across reboots, what permissions or credentials are needed, what happens if the item is already disabled or does not exist, or what is returned; the only behavioral hint is that the operation is non-destructive in spirit, which is implied rather than stated.

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 front-loaded sentence with no filler, and the actionable scope appears immediately. It is efficient, though the brevity comes at the cost of the detail the other dimensions lack.

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 three-parameter mutation tool with no annotations and no output schema, the description is far too thin: parameter formats, target-router selection, failure modes, and the resulting state are all unaddressed. An agent could not reliably call this correctly without external knowledge of RouterOS path/item conventions.

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 all three parameters, and the description does not explain that 'path' is a RouterOS menu path (e.g. /interface) while 'item' is an identifier or name within it. The examples (interface, rule, route) loosely hint at path values but do not clarify the required format of either parameter, and 'router' is not mentioned at all.

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 ('Disable') and a resource ('an item'), plus parenthetical examples (interface, rule, route) that scope what an item can be. It does not distinguish itself from siblings like ros_remove or ros_set, but the action itself is 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?

No guidance on when to use this versus ros_enable (the inverse), ros_remove (delete vs disable), or ros_set (change settings). The agent must infer the intended workflow — e.g. that disabling is reversible and preferable to removal — entirely from sibling names.

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