Skip to main content
Glama

ros_cli

Run plain RouterOS terminal commands over SSH and return the text output, supporting multiple commands separated by semicolons or newlines for remote MikroTik configuration and diagnostics.

Instructions

Run plain terminal commands over SSH and return the text output, exactly as typed in the WinBox 'New Terminal'. Multiple commands can be separated by ';' or newlines. E.g. '/ip route print detail', '/export hide-sensitive', ':put [/system resource get cpu-load]'.

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": {
      "command": "<command>"
    },
    "name": "ros_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
routerNo
commandYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 supplied, so the description carries the full safety burden. It discloses SSH transport, exact-text output, and multi-command separators, but says nothing about permissions, whether arbitrary commands can mutate or destroy configuration, error behavior, or timeout handling.

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 sentences plus compact examples, front-loaded with the core action. The examples earn their place by showing command syntax, and the wording is efficient.

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?

Output schema covers return values, so the description need not explain them. Given an arbitrary-command tool with no annotations and undocumented schema parameters, the definition is still incomplete: target routing, timeout, and risk or safety guidance are missing.

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. The description gives command examples and separator behavior, but does not explain what 'router' selects when omitted or how 'timeout' is applied; router and timeout semantics are absent.

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?

The description names a specific action (run plain terminal commands over SSH) and output (text output exactly as typed). It implicitly separates raw CLI usage from structured siblings such as ros_print and ros_set, but never names an alternative, so sibling differentiation is only partial.

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 examples show which kinds of commands fit and how to concatenate multiple commands, implying this is the raw escape hatch. However, it never states when to prefer dedicated siblings or when this tool should be avoided, so guidance remains implicit.

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