ActiveMQ MCP Server

purge_queue

Remove all messages from an ActiveMQ queue by specifying the queue name and confirming the operation. Clear the queue of pending messages to reset or free up the broker for new traffic.

Instructions

Remove all messages from a queue

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": {
      "connectionId": "<connectionId>",
      "queueName": "<queueName>",
      "confirm": "<confirm>"
    },
    "name": "purge_queue"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Confirmation flag - must be true to proceed with purge
`queueName`	Yes	Name of the queue to purge
`connectionId`	Yes	ID of the connection

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Aug 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not state that this is a destructive/irreversible operation, that a confirm flag is required for safety, whether it removes messages being currently processed, or what happens to the queue afterward. The confirm parameter implies destructive behavior but the description relies on schema rather than disclosing it.

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 efficient sentence with zero waste. However, given the destructive nature of the operation, a bit more behavioral context would justify additional length.

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?

For a destructive tool with no annotations and no output schema, the description is notably thin. It doesn't disclose that all messages (including possibly in-flight ones) are removed, doesn't mention the confirm safety flag purpose, doesn't note irreversibility, and provides no guidance on impact to connected consumers.

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 100%, so all three parameters (confirm, queueName, connectionId) are already documented structurally. The description adds minimal value beyond this—it doesn't explain why confirm must be true, what the queueName semantics are, or how connectionId relates to the connection lifecycle.

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 'Remove all messages from a queue' uses a specific verb (Remove) + resource (queue) and clearly states the scope (all messages). It distinguishes from siblings like consume_message or browse_messages, though it doesn't explicitly differentiate from any similar purge/delete tool in the siblings list.

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 guidance is given on when to use this tool vs alternatives. There's no mention of destructive nature, no confirmation about whether this is reversible, no notes about prerequisites (e.g., connecting first), and no warnings that this is a destructive operation affecting all consumers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.