Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Torch

torch
Read-onlyIdempotent

Capture a real-time traffic snapshot on a MikroTik router interface for a chosen duration and return top flows by bytes to find bandwidth-heavy sources and destinations.

Instructions

Capture a real-time traffic snapshot on a router interface. The tool call blocks for the duration (seconds) and returns top flows by bytes. readOnlyHint true — auto-retry enabled.

Input Schema

TableJSON 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

A3.7/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it notes that the tool call blocks for the duration and returns top flows by bytes. It also repeats the readOnlyHint and mentions auto-retry, which is additional info not in annotations. It does not contradict 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?

The description is two concise sentences that front-load the main purpose and include key behavioral traits. It is appropriately sized, though the mention of auto-retry could be seen as slightly redundant given annotations.

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?

Given the tool's complexity (5 parameters, 1 required) and the lack of an output schema, the description covers the essential behavior: blocking nature and return format (top flows by bytes). It could benefit from mentioning pagination or result limits, but is largely complete.

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 the schema already documents all parameters thoroughly. The description mentions 'duration (seconds)' but adds no syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 ('Capture') and resource ('real-time traffic snapshot on a router interface'), which is clear and distinguishable from siblings like ping or traceroute. However, it does not explicitly differentiate itself from those sibling network-diagnostic tools.

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 description implies usage for capturing traffic snapshots but provides no explicit guidance on when to use this tool versus alternatives such as traceroute, ping, or bandwidth_test. The agent must infer the appropriate context.

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