Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Torch

torch
Read-onlyIdempotent

Capture a live traffic snapshot on a MikroTik router interface for 1-30 seconds and return per-flow TX/RX rates in bits and packets per second.

Instructions

Capture a real-time traffic snapshot on a router interface. RouterOS runs the capture for duration seconds; the tool returns the flows of the final update with their TX/RX rates in bits per second and packets per second. Not auto-retried.

Input Schema

NameRequiredDescriptionDefault
durationNoCapture duration in seconds (1–30)
routerIdNoRouter ID; omit to use the default router.
interfaceYesInterface name to monitor (e.g. ether1, bridge1)
dstAddressNoFilter by destination IP address
srcAddressNoFilter by source IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.11.0
    • addedInput schema / properties / dstAddress / $ref
      Added value: +"#/properties/srcAddress"
    • removedInput schema / properties / dstAddress / type
      Removed value: -"string"
    • addedInput schema / properties / srcAddress / $ref
      Added value: +"#/properties/interface"
    • removedInput schema / properties / srcAddress / type
      Removed value: -"string"
  2. Changed2 schema fields changedv1.6.0
    • changedInput schema / properties / routerId / description
      Previous value: -"Target router identifier from the router registry"New value: +"Router ID; omit to use the default router."
    • changedInput schema / required
      Previous value: -[
-  "routerId",
-  "interface"
-]New value: +[
+  "interface"
+]
  3. Addedv1.5.0
  4. Removedv1.1.0
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/destructive=false, so the safety profile is covered. The description adds value beyond that: it discloses that RouterOS runs the capture for `duration` seconds, that the return is the flows from the final update with TX/RX rates in bps and pps, and the key operational trait that the call is not auto-retried.

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?

Three tight sentences, front-loaded with the core action, followed by duration behavior and return format. No filler or repetition of the name/title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully explains what comes back (per-flow TX/RX rates) and how long the capture runs, which is the main thing an agent needs before calling. Minor gaps remain around default-router resolution and how the address filters shape results, but the schema carries those parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so interface, duration, routerId, and the address filters are already documented. The description's mention of `duration` seconds only restates the schema's own wording, so this is the baseline 3 rather than added semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Capture a real-time traffic snapshot on a router interface') and unpacks the jargon term 'torch' that the tool name alone would not convey. It is clearly distinct from familial siblings like bandwidth_test, ping, or list_connections, so an agent can select it without opening the schema.

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?

Usage is implied by the description of what a capture does, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. bandwidth_test for throughput measurement). The operational note 'Not auto-retried' implies the caller must decide about retries, which is helpful but indirect.

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