Skip to main content
Glama

ros_set

Modify MikroTik RouterOS configuration items by ID, name, or key=value, including single-value menu settings such as system identity, DNS, and clock.

Instructions

Change an item. item: '.id' like '*3', a name, or 'key=value'. Omit item for single-value menus such as '/system/identity', '/ip/dns', '/system/clock'.

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

Input Schema

NameRequiredDescriptionDefault
itemNo
pathYes
routerNo
propertiesYes

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?

With no annotations, the description carries the full behavioral burden and discloses very little: it doesn't state that this mutates live router configuration, whether changes are persisted or reversible, what permissions are needed, or what happens on a partial/unknown property key. The only real behavioral hint — that item can be omitted for single-value menus — is useful but narrow.

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?

Front-loaded with the verb and immediately followed by the highest-value detail (item syntax), with no filler. Only minor friction from the awkward line break and the unexplained term 'single-value menus', which a reader may not decode without RouterOS familiarity.

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 4-parameter, nested-object mutation tool with no annotations, no output schema, and no schema descriptions, this is far too thin — an agent cannot construct a correct call without already knowing RouterOS path semantics and the properties object shape. It covers one parameter well and leaves the calling contract largely undefined.

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 coverage is 0%, so the description must explain all four parameters, but it only documents `item` ('.id' like '*3', a name, or 'key=value'). The most consequential parameters — `path` (which menu to edit) and `properties` (the key/value payload actually written) — receive no explanation at all, and `router` is unmentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Change an item" names a mutation verb but leaves the resource ambiguous — 'item' only becomes meaningful through the item-format examples, and the description never says it edits a RouterOS configuration menu identified by `path`. An agent must infer the pairing with siblings like ros_add/ros_remove to understand this is the modify-in-place counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is one concrete usage rule: omit `item` for single-value menus, with three examples ('/system/identity', '/ip/dns', '/system/clock'). What's missing is the more important routing guidance — when to use this instead of ros_add (create) or ros_remove, and whether the target must already exist.

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