Skip to main content
Glama

upload_file

Uploads base64-encoded files to MikroTik devices to support restore operations and configuration recovery.

Instructions

Uploads a base64-encoded file to the MikroTik device (for restore operations).

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": {
      "filename": "<filename>",
      "content_base64": "<content_base64>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
filenameYes
content_base64Yes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered structurally. The description contributes the useful fact that content must be base64-encoded and that the tool targets restore flows, but it says nothing about overwrite behavior, size limits, or where the file lands on the device.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the core action and encoding requirement front-loaded and the usage hint trailing in parentheses. Nothing is wasted and nothing is buried.

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?

An output schema exists, so return values need not be explained, which relieves some burden. Still, for a write tool with an unlabeled device parameter and zero schema descriptions, the definition is thinner than the complexity warrants.

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 carry the burden, and it only illuminates 'content_base64'. It says nothing about whether 'filename' accepts a path or just a bare name, nor what a null 'device' resolves to, leaving two of three parameters ambiguous.

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 description gives a specific verb and resource ('Uploads a base64-encoded file to the MikroTik device') and adds a scope qualifier ('for restore operations') that tells an agent this is not a general-purpose file push. It is clearly distinct from siblings like download_file and remove_file, though it never names them explicitly.

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?

The parenthetical '(for restore operations)' implies the intended workflow, so an agent can infer this pairs with backup/restore tasks rather than everyday file management. However, there is no explicit statement of when to prefer this over other tools, no prerequisite checks, and no guidance on what to do before or after uploading.

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

Deploy Server

Other Tools