Skip to main content
Glama

ros_print

Read MikroTik RouterOS menu data by path, applying equality filters, field selection, or raw API queries to inspect router configuration and status.

Instructions

Read a menu (like opening a WinBox window). path e.g. '/ip/address', '/interface', '/ip/firewall/filter', '/routing/ospf/neighbor', '/system/resource', '/log'. where: equality filters {'interface': 'ether1', 'disabled': False}. proplist: only these fields. query: raw API query words, e.g. ['?>bytes=1000', '?#|'].

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

Input Schema

NameRequiredDescriptionDefault
pathYes
queryNo
whereNo
detailNo
routerNo
proplistNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 behavioral burden; 'Read' establishes a read-only, non-mutating operation and the note that query takes 'raw API query words' warns that unrecognized syntax is passed straight through to RouterOS. It discloses nothing about authentication, permissions, result size, or paging limits, which matters for menus like '/log' that can be large.

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?

It is front-loaded with purpose and then gives one compact clause per parameter with no filler. The terse fragment style and unexplained raw tokens like '?#|' are dense but appropriate for the intended audience.

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?

Given six parameters at 0% schema coverage and no annotations, the description covers the core read path reasonably but leaves 'router' entirely unexplained, which is significant on a multi-router tool. An output schema exists, so omitting return-value details is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does for four of six parameters: path with five concrete examples, where as equality filters with a sample dict, proplist as a field whitelist, and query as raw API words with example tokens. It says nothing about 'detail' or 'router', leaving the multi-router selector undocumented.

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 verb 'Read' plus the RouterOS-specific resource ('menu', clarified by the WinBox analogy and concrete paths like '/ip/address') tells an agent exactly what this does and contrasts implicitly with mutating siblings such as ros_add, ros_set, and ros_remove. It stops short of naming a sibling to differentiate from, so it is not a 5.

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

Usage Guidelines2/5

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

The description explains the shape of the input but never states when to pick this over ros_command, ros_cli, or ros_export, nor any when-not condition. Usage is only inferable from the word 'Read' and the example paths.

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