Skip to main content
Glama

ros_enable

Enable a MikroTik RouterOS item such as an interface, firewall rule, or route by specifying its path and item identifier, so disabled configurations can be activated.

Instructions

Enable 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_enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
pathYes
routerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it supplies almost nothing. It does not say whether the operation is idempotent when the item is already enabled, what permissions are required, whether the change is persistent or reversible, or what the result looks like; "Enable" alone implies mutation but discloses no mutation semantics.

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 short sentence with the verb and examples front-loaded and no wasted words. Its brevity is close to under-specification rather than true economy, which keeps it off a 5.

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?

For a three-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition leaves real gaps around the required `path` format and post-condition behavior. What is there is accurate but far from sufficient to call the tool confidently.

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 compensate, and it only partially does: the parenthetical clarifies what an "item" might be, but the required `path` parameter (presumably the RouterOS menu path) and the optional `router` target are left entirely unexplained. An agent could not determine the expected format of `path` from either source.

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 ("Enable") plus a resource with concrete examples ("interface, rule, route ..."), so the agent knows this flips an object to an enabled state rather than creating or removing it. It stops short of a 5 because it never names ros_disable as the counterpart or otherwise differentiates itself from that sibling.

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 tool versus ros_set, ros_add, or ros_disable, and no preconditions such as the object needing to already exist. The agent must infer the entire selection context from the tool name alone.

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