Skip to main content
Glama

create_queue_tree

Creates a hierarchical queue tree entry attached to a parent interface or queue to organize bandwidth limits, priorities, and burst settings on MikroTik RouterOS.

Instructions

Creates a hierarchical queue tree entry attached to a parent interface or queue.

Notes: max_limit / limit_at / burst_limit / burst_threshold: bandwidth e.g. "10M", "512k", "1G" burst_time: duration e.g. "8s" parent: interface name e.g. "ether1" or parent queue name 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>",
      "parent": "<parent>"
    },
    "name": "create_queue_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
queueNo
deviceNo
parentYes
commentNo
disabledNo
limit_atNo
priorityNo
max_limitNo
burst_timeNo
bucket_sizeNo
burst_limitNo
packet_markNo
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 mutation profile is covered structurally. The description adds nothing beyond annotations about behavior: it does not say whether duplicate names error, what 'device' does across multiple routers, whether a missing parent fails, or what the tool returns on success.

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 the notes are a tight, scannable list with no filler. The compressed notation ('burst_time: duration e.g. "8s"') is efficient, though the parent note conflates two cases and could be clearer.

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 14-parameter create tool with 0% schema description coverage, the description should explain at minimum what 'device' and 'queue' select and whether names must be unique — neither is addressed.

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 coverage is 0% across 14 parameters, so the description carries the burden and does supply genuinely useful semantics for about half of them: bandwidth units for max_limit/limit_at/burst_limit/burst_threshold, duration syntax for burst_time, parent naming, and the 1–8 priority range. It leaves name, queue, device, comment, disabled, bucket_size, and packet_mark completely undefined, which is a substantial gap for a 14-parameter tool.

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?

The description opens with a specific verb and resource: 'Creates a hierarchical queue tree entry attached to a parent interface or queue.' The 'hierarchical' and 'parent interface or queue' phrasing hints at how this differs from simple queues or queue types, but it never names those siblings explicitly, so an agent must infer the distinction.

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 notes explain value formats for individual fields but give no guidance on when to choose a queue tree over create_simple_queue or create_queue_type, no prerequisites, and no failure conditions. An agent knowing nothing about RouterOS traffic shaping gets formatting help but no selection help.

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