Skip to main content
Glama

create_simple_queue

Creates a MikroTik simple queue to rate-limit traffic for a target IP/CIDR or interface, with upload/download limits and burst settings.

Instructions

Creates a simple queue to rate-limit a target address or interface.

Notes: target: IP/CIDR or interface e.g. "192.168.1.0/24" or "ether1" max_limit / limit_at / burst_limit / burst_threshold: upload/download bandwidth as "UL/DL" e.g. "10M/10M", or single value e.g. "10M" burst_time: duration e.g. "8s" priority: 1 (highest) – 8 (lowest)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "target": "<target>"
    },
    "name": "create_simple_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
dstNo
nameYes
queueNo
deviceNo
parentNo
targetYes
commentNo
disabledNo
limit_atNo
priorityNo
max_limitNo
burst_timeNo
bucket_sizeNo
burst_limitNo
packet_marksNo
burst_thresholdNo

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.9/5.0
Behavior2/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 covered. The description adds nothing behavioral beyond that: it does not say what happens on a duplicate queue name, whether the target must already exist, whether changes are immediately active, or what errors may occur.

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 purpose sentence is front-loaded and every note line contributes concrete format information. Structure is compact and scannable; no filler text.

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 not be explained, and annotations cover the safety profile. However, for a 16-parameter mutation tool with zero schema coverage, half the parameters are left unexplained, which is a meaningful gap for correct invocation.

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 0% across 16 parameters, so the description carries real weight here. The notes give useful value formats for target, max_limit, limit_at, burst_limit, burst_threshold, burst_time and priority (UL/DL notation, duration format, priority range), but eight parameters (dst, queue, device, parent, comment, disabled, bucket_size, packet_marks) remain entirely undocumented in both schema and description.

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 ("Creates a simple queue") plus the effect ("rate-limit a target address or interface"), which is enough to distinguish it from list/get/remove/enable siblings. It does not distinguish it from create_queue_tree or create_queue_type, leaving a small ambiguity among the create operations.

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?

No when-to-use, when-not-to-use, or prerequisite guidance is given. The description never mentions the alternative create_queue_tree/create_queue_type tools or the conditions (e.g. simple vs hierarchical queueing) that select between them.

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