Skip to main content
Glama

add_router

Add or replace a MikroTik RouterOS router connection by specifying host, transport, ports, and credentials; optionally save it and set it as default.

Instructions

Add (or replace) a router.

transport: 'api' (8728), 'api-ssl' (8729), 'rest' (v7 REST over http/www, e.g. a WebFig port) or 'rest-ssl'. port: the API/REST port if not standard. ssh_port: used by ros_cli / ros_export / file tools. save: persist to the config file (password stored there with 0600 permissions).

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": {
      "name": "<name>",
      "host": "<host>"
    },
    "name": "add_router"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
nameYes
portNo
saveNo
passwordNo
ssh_portNo
usernameNoadmin
transportNoapi
make_defaultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose key side effects: save persists to the config file and the password is stored there with 0600 permissions, plus that an existing entry may be replaced. It omits whether credentials/connectivity are validated, error behavior on failure, and what is returned, which matters for a mutating tool with zero annotation coverage.

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 single-line purpose followed by compact per-parameter notes; every line carries information. Slightly telegraphic ('transport: ... port: ...') but not wasteful.

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 9-parameter mutating tool with no annotations and no output schema, the definition covers the risky areas (persistence, credential file permissions, transport selection) but leaves the connection/auth parameters and make_default unexplained and gives no return-value or failure expectations.

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 coverage is 0% across 9 parameters, so the description must compensate and it only partly does: transport values with their default ports (8728/8729/v7 REST), the purpose of port, ssh_port consumers, and save semantics are explained. Five parameters (host, name, username, password, make_default) get no added meaning beyond their titles and defaults.

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 (or replace) a router') and even clarifies the replace semantics for an existing name. It implicitly separates itself from remove_router/list_routers siblings, though it never names an alternative.

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?

No explicit when-to-use versus when-not guidance (e.g., add_router vs discover_neighbors or list_routers). Indirect guidance exists: the transport/port mapping and the note that ssh_port is consumed by ros_cli, ros_export, and file tools tells an agent what each configured router will be used for.

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