Skip to main content
Glama

export_logs

Exports MikroTik device logs to a .txt file, with optional topic and time filters for targeted troubleshooting.

Instructions

Exports logs to a .txt file on the MikroTik device with optional topic and time filters.

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

Input Schema

NameRequiredDescriptionDefault
deviceNo
topicsNo
filenameNo
time_filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.7
    • removedInput schema / properties / format
      Removed value: -{
      -  "default": "plain",
      -  "enum": [
      -    "plain",
      -    "csv"
      -  ],
      -  "title": "Format",
      -  "type": "string"
      -}
  2. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  3. First observedv0.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is already known; the description usefully adds that output is written as a file on the device itself. However, it omits overwrite behavior, where on the device the file lands, and whether repeated calls create duplicates — gaps that matter for a non-idempotent write. No contradiction with annotations.

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 wasted clauses. It is efficient, though its brevity is part of why coverage is thin.

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 no explanation, and annotations cover safety. But for a 4-parameter write operation with 0% schema coverage, the description should say more about filename/device semantics and file overwrite consequences.

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 parameter burden, yet it only gestures at 'topic and time filters' and never explains the 'device' or 'filename' parameters (filename is only implied by '.txt file'). Formats, defaults, and accepted time-filter syntax are unstated.

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 ('Exports logs') plus the destination ('to a .txt file on the MikroTik device') and filter scope, which separates it from read-only siblings like get_logs or search_logs. It does not name an alternative explicitly, so it falls short of 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 says what the filters are but never says when to use this export over the log-reading siblings (get_logs, search_logs, monitor_logs) or what prerequisites exist. There is no when-not guidance and no mention of what to do if a file already exists.

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