Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage Queue

manage_queue
DestructiveIdempotent

Add, remove, enable, or disable a simple queue on MikroTik RouterOS by name; idempotent add and dry-run preview avoid duplicate changes.

Instructions

Add, remove, enable, or disable a simple queue. Idempotent by name: add returns already_exists if a queue with the same name and target already exists.

Input Schema

NameRequiredDescriptionDefault
nameYesQueue name — idempotency key
actionYesAction to perform
dryRunNoPreview changes without applying.
targetNoTarget address (required for add; e.g. '192.168.1.0/24')
commentNoOptional comment
limitAtNoGuaranteed rate (e.g. '1M/1M')
maxLimitNoMax upload/download limit (e.g. '10M/10M')
routerIdNoRouter ID; omit to use the default router.
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.1
    • addedInput schema / properties / confirmationToken
      Added value: +{
+  "description": "Token from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / dryRun / description
      Previous value: -"Preview changes without applying"New value: +"Preview changes without applying."
    • 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",
-  "action",
-  "name"
-]New value: +[
+  "action",
+  "name"
+]
  3. Addedv1.5.0
  4. Removedv1.1.0
  5. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is covered. The description adds the concrete already_exists return on duplicate add, but does not disclose the destructive confirmation flow (confirmationToken / APPROVAL_REQUIRED) or what removal actually destroys. It slightly restates the idempotency annotation rather than extending it.

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?

Two sentences, front-loaded with the operation list, with zero filler. The idempotency caveat is correctly placed as the second sentence because it refines behavior rather than redefining purpose.

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?

For a 9-parameter tool with no output schema, the description is minimally adequate; the schema covers per-parameter meaning, so return values need not be explained. It stops short of describing the multi-step destructive confirmation flow and dryRun preview that an agent invoking remove/disable would benefit from understanding.

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 carries the heavy lifting for all 9 parameters. The description reinforces the 'idempotency key' role of name, but adds no syntax or format detail beyond what the schema already documents. Baseline 3 is appropriate.

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 names a specific resource ('simple queue') and enumerates the exact operations (add, remove, enable, disable), which cleanly separates it from the read-only sibling list_queues. An agent can identify this as the mutation counterpart 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 action set; an agent knows this is the tool for mutating queues. However, it never states when to choose this over list_queues, nor gives guidance on which action fits which scenario (e.g., remove vs disable), leaving that to inference.

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