Skip to main content
Glama

ros_file_download

Download MikroTik RouterOS files such as backups or .rsc scripts over SFTP to a local path for safekeeping or inspection.

Instructions

Download a file from the router (SFTP), e.g. a .backup or .rsc.

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": {
      "remote_name": "<remote_name>",
      "local_path": "<local_path>"
    },
    "name": "ros_file_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
routerNo
local_pathYes
remote_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 and only discloses the protocol (SFTP). It says nothing about whether an existing local file is overwritten, what permissions/credentials are needed, what happens on a missing remote file, or any size/timeout constraints on the transfer.

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?

A single front-loaded sentence with no filler; verb and resource come first. It is efficient, though arguably too terse given the undocumented parameters.

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?

An output schema exists, so return values need not be described, but for a 3-parameter transfer tool with zero annotation and zero schema-description coverage the definition leaves real gaps: local path semantics, overwrite behavior, and multi-router targeting are all unaddressed.

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%, so the description must compensate, and it does not: it never explains 'remote_name' vs 'local_path' (e.g. whether local_path is a directory or full filename) or what 'router' selects when multiple routers exist. The SFTP parenthetical is the only added meaning.

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 ('Download a file from the router') and even names the transport (SFTP) plus example file types (.backup, .rsc), so an agent knows exactly what it does. It does not distinguish itself from the obvious inverse sibling ros_file_upload, which keeps it from 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 'e.g. a .backup or .rsc' clause hints at a use case (retrieving configuration/backup artifacts), but there is no explicit when-to-use, no statement of when to prefer ros_file_upload or ros_export instead, and no prerequisites such as credentials or existing remote file.

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