Skip to main content
Glama

ros_export

Export MikroTik RouterOS configuration as a .rsc script, either the whole config or a specific menu such as /ip firewall, for backup or review.

Instructions

Export the configuration as a .rsc script (whole config, or one menu like '/ip firewall').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ros_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
terseNo
routerNo
show_sensitiveNo

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?

With no annotations, the description carries the full behavioral burden. It conveys that the result is a text script rather than a mutation, but says nothing about whether the router is modified, what permissions are required, or how the .rsc output is returned. Most importantly, it omits any warning that the show_sensitive parameter can expose credentials and secrets in the exported script — a material behavioral risk for this tool.

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?

One tightly written sentence, front-loaded with the verb and the output artifact, with the scope qualifier in parentheses. Nothing is wasted, though the brevity is partly the source of the parameter gaps.

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?

The presence of an output schema removes the need to describe return values, but for a four-parameter, zero-coverage, annotation-free tool this is thin. The undefined show_sensitive flag in particular is a completeness gap an agent cannot resolve from any supplied field.

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% across four parameters, so the description must compensate and largely does not. It implicitly explains 'path' via the '/ip firewall' menu example, but terse, show_sensitive, and router are never addressed in the description or the schema, leaving three of four parameters semantically opaque.

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 (Export) and resource (the configuration) and clarifies scope: whole config or a single menu such as '/ip firewall'. An agent immediately knows the output is a .rsc script. It stops short of distinguishing itself from the sibling ros_backup, which an agent could plausibly confuse with export.

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?

Usage is only implied by the word 'Export' and the parenthetical about whole-config vs single-menu scope. There is no explicit when-to-use framing and no mention of when ros_backup or ros_print would be the better choice, so the agent must infer the routing decision.

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