Skip to main content
Glama

ros_add

Adds a new item to a MikroTik RouterOS path using specified properties and returns the new .id, supporting automated router configuration changes.

Instructions

Add an item, e.g. path='/ip/address', properties={'address': '10.0.0.1/24', 'interface': 'ether2'}. Returns the new .id.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
routerNo
propertiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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. It does disclose a useful behavioral fact beyond the schema — that the call returns the new .id, which is essential for chaining follow-up operations — but says nothing about permissions, validation failures, or the fact that this mutates persistent router configuration.

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?

Two short sentences, front-loaded with a worked example, and the return-value note is appended where it belongs. No filler or repetition; it could only be improved by adding the missing router parameter detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with a free-form nested properties object and no output schema, the example plus the stated return value cover the core calling pattern. The omission of the router parameter's meaning keeps it short of fully complete.

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. The example gives concrete semantics for path and for the shape of properties (key/value pairs matching the menu's fields), but the third parameter, router, is never mentioned or explained, and nothing indicates that valid property keys depend on the chosen path.

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 and resource ("Add an item") and immediately grounds it with a concrete RouterOS path/properties example, so an agent knows this creates a configuration entry at a menu path. It does not explicitly distinguish itself from siblings like ros_set or ros_remove, but the example makes the create semantics clear.

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?

The example implies the usage context (creating an object under a RouterOS menu with its properties), which is enough to infer when to call it. There is no explicit statement about when not to use it, nor any pointer to ros_set for modification or ros_remove for deletion, so the guidance remains implicit.

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