Skip to main content
Glama

update_queue_tree

Idempotent

Modify an existing MikroTik queue tree entry to adjust bandwidth limits, parent, priority, burst settings, or other parameters without recreating the queue.

Instructions

Updates an existing queue tree entry (bandwidth limits, parent, priority, etc.).

Notes: max_limit / limit_at / burst_limit / burst_threshold: bandwidth e.g. "10M", "512k" 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>"
    },
    "name": "update_queue_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
queueNo
deviceNo
parentNo
commentNo
disabledNo
limit_atNo
new_nameNo
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

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds only the 'existing entry' precondition; it never explains the crucial partial-update semantics for a 15-param tool where 14 params are nullable with default null (are omitted fields left unchanged?), nor what new_name does relative to name, nor whether the device/queue pair must match the existing object.

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?

Short and front-loaded: one sentence stating the action followed by a compact notes block that groups the related bandwidth parameters on a single line. Nothing is wasted, though the 'etc.' in the opening is a small hedge that could have been spent naming the remaining fields.

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

Completeness2/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 mutation tool with 15 parameters and zero schema descriptions, the definition leaves over half the params and the null-means-unchanged convention unaddressed, which is the main thing an agent needs in order to call this correctly.

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%, so the description carries the burden, and it does supply genuinely useful unit/format guidance for the trickiest fields: bandwidth strings like "10M"/"512k" for max_limit, limit_at, burst_limit, burst_threshold, duration format for burst_time, and the 1–8 priority scale with direction stated. That still leaves queue, device, parent, comment, disabled, new_name, bucket_size, and packet_mark entirely undocumented in both schema and description, so compensation is partial.

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: 'Updates an existing queue tree entry,' and parenthetically names the kinds of fields affected (bandwidth limits, parent, priority). The sibling set contains update_queue_type, update_simple_queue, and update_queue_tree, and the resource name in the first clause is enough to disambiguate which object family this mutates, though it never explicitly contrasts itself with those siblings.

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 only implied: 'existing' signals the entry must already exist and the required 'name' param identifies the target, so an agent can infer this is the modify path versus create/remove. There is no explicit when-to-use/when-not-to-use statement and no pointer to update_queue_type or update_simple_queue when the target is a different queue kind.

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