Skip to main content
Glama

update_simple_queue

Idempotent

Modify an existing MikroTik simple queue's bandwidth limits, target, priority, or burst settings to adjust traffic shaping.

Instructions

Updates an existing simple queue's rate limits, target, or scheduling settings.

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>"
    },
    "name": "update_simple_queue"
  }
}

Input Schema

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

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds nothing about partial-update semantics (whether omitted optional parameters are left unchanged or cleared), which is the most consequential behavior for a 17-param update tool.

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?

Front-loaded summary sentence followed by a scannable notes block keyed to parameter names. No filler, though the notes are selective and an agent may not notice the ten parameters left undocumented.

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 and annotations exist, reducing what the description must cover. However, with 17 parameters at 0% schema coverage, ten fields (dst, queue, device, parent, comment, disabled, new_name, bucket_size, packet_marks) have no meaning documented anywhere, and partial-update behavior is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does for the most error-prone fields: target format (IP/CIDR or interface), UL/DL bandwidth syntax, burst_time duration syntax, and the 1-8 priority scale. These are exactly the values an agent could not guess from bare string schemas.

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 ("Updates an existing simple queue") plus the categories of settings affected (rate limits, target, scheduling). The resource type matches sibling names like create_simple_queue and update_queue_tree, so an agent can infer the family, though the description 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only the word "existing" implies a precondition (the queue must already exist); there is no explicit when-to-use guidance, no mention of create_simple_queue for new queues, and no note that `name` is the selector for which queue gets updated. The agent must infer all of this.

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