Skip to main content
Glama

update_queue_type

Idempotent

Update an existing queue type’s CAKE/PCQ discipline settings to adjust traffic shaping parameters without creating a new queue type.

Instructions

Updates an existing queue type's discipline-specific settings.

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_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceNo
cake_mpuNo
cake_natNo
cake_rttNo
new_nameNo
pcq_rateNo
cake_washNo
pcq_limitNo
cake_diffservNo
cake_flowmodeNo
cake_overheadNo
pcq_classifierNo
cake_ack_filterNo
cake_overhead_schemeNo

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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the target is an existing queue type and that the settings are discipline-specific, but it does not explain partial-update behavior, what happens to omitted fields, or permission requirements.

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 description is a single front-loaded sentence with no wasted wording. However, for a tool with 15 parameters and no schema descriptions, that conciseness comes at the cost of useful detail.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex: 15 input parameters, only one required, and no schema description coverage. Although an output schema exists and reduces the need to describe return values, the description does almost nothing to compensate for the undocumented input parameters or to clarify update semantics.

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

Parameters1/5

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

The input schema has 15 parameters with 0% description coverage, and the description does not explain any of them. It only refers vaguely to 'discipline-specific settings' without mapping to cake_* or pcq_* parameters, leaving the agent with no semantic guidance beyond the parameter names.

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 states a specific verb and resource: updating an existing queue type. It adds scope with 'discipline-specific settings,' which helps distinguish it from generic queue operations, but it does not explicitly differentiate it from sibling update tools such as update_queue_tree or update_simple_queue.

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 description implies the tool is for updating an existing queue type, but it gives no guidance on when to choose it over alternatives. It does not mention prerequisites, when not to use it, or how it relates to create_queue_type, get_queue_type, or other update_* siblings.

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