Skip to main content
Glama

create_export

Generate a MikroTik configuration export file in RSC, JSON, or XML format to back up settings, audit device state, or share configs while optionally hiding sensitive data.

Instructions

Creates a configuration export file (rsc/json/xml) on the MikroTik device.

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": "create_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
deviceNo
commentNo
compactNo
verboseNo
export_typeNofull
file_formatNorsc
hide_sensitiveNo

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

C2.8/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 mostly covered. The description confirms it writes a file on the device, consistent with the annotations, but adds nothing about overwrite behavior, target path, permissions, or whether repeated calls produce duplicate files — despite idempotentHint=false making that a real concern for the caller.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, which is good structurally. However, the brevity comes at the cost of substance — nothing is said that the schema and annotations do not already imply, so the economy does not earn its place.

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 explained. But for an 8-parameter, zero-coverage, non-idempotent write tool that shares a name prefix with six export_* siblings, one sentence is far too thin to let an agent call it correctly or pick it over alternatives.

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 8 parameters, so the description carries the full burden and mostly fails: it only hints at file_format (rsc/json/xml). Critical parameters such as name, device, hide_sensitive (default true), export_type versus compact/verbose overlap, and comment are entirely unexplained, leaving ambiguous interactions between the export_type enum and the compact/verbose booleans unaddressed.

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?

Names a specific verb and resource ("Creates a configuration export file") and enumerates the formats rsc/json/xml, which is concrete enough to act on. It does not distinguish this tool from the sibling export_* tools (export_section, export_dns_config, export_user_config), so the agent gets no help choosing between a full-device export and a scoped one.

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?

There is no statement of when to use this tool versus the many export_* siblings, and no exclusions or prerequisites. The agent must infer from the description alone whether this is a full config dump or something narrower.

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