Skip to main content
Glama

ros_file_upload

Upload files to a MikroTik RouterOS router over SFTP, including .npk packages, .rsc scripts for /import, or certificates, to transfer required assets directly to the device.

Instructions

Upload a file to the router (SFTP), e.g. an .npk package, a .rsc to /import, or a certificate.

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

Input Schema

NameRequiredDescriptionDefault
routerNo
local_pathYes
remote_nameNo

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?

No annotations are supplied, so the description carries the full burden. It discloses the transfer protocol (SFTP) but says nothing about overwrite behavior, whether the destination directory must already exist, permission/auth requirements, file size limits, or what a failed transfer looks like — significant gaps for a write-side operation.

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 the action and protocol stated first, followed by illustrative examples; nothing is redundant. It is efficiently written, though the brevity contributes to the gaps noted elsewhere.

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 an unannotated file-transfer mutation with 0% parameter coverage the description leaves out destination resolution, overwrite semantics, and authentication. An agent could not reliably call this correctly without trial and error.

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 three parameters, so the description must compensate and largely does not. It gestures at the local file and at '/import' as a destination, but never explains the 'router' selector or clarifies that 'remote_name' is a filename rather than a path, nor which directory an upload lands in by default.

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 ('Upload a file to the router') and adds the transport (SFTP) plus concrete example artifacts (.npk package, .rsc to /import, certificate). It does not explicitly name ros_file_download as its inverse, so sibling differentiation is only implied by the verb.

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 examples hint at what kinds of files are uploaded, but there is no statement of when to choose this over ros_file_download or ros_export, and no prerequisites such as required credentials or supported filesystems. The agent must infer all routing decisions.

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