ActiveMQ MCP Server

export_connections

Export ActiveMQ connection configurations to back up or migrate broker connection settings for reuse or transfer to another environment.

Instructions

Export connection configurations for backup or migration

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_connections"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Aug 4, 2026

TDQS

B3.2/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. It doesn't disclose what format the export takes (file? JSON?), where output goes, whether it requires permissions, whether it affects live state, or what the response looks like. For an export tool with zero annotation coverage, this is a meaningful gap.

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?

A single concise sentence with no wasted words. It's appropriately brief given there are no parameters to describe, though it could arguably add format details without growing much.

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?

There is no output schema and no annotations, so the description must cover behavior and results. It doesn't explain what the export produces, its format, or how it relates to the inverse import tool. For a tool with zero params and no schema support, the description leaves important behavioral questions unanswered, though the simple signature lowers the bar somewhat.

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

Parameters4/5

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

There are 0 parameters and the schema has 100% coverage (empty properties object), so there's nothing for the description to document. The schema fully defines the parameter surface, giving a baseline 4.

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+resource ('Export connection configurations') with a clear purpose ('for backup or migration'). It distinguishes reasonably from siblings like import_connections (the inverse) and connect_from_config (which loads into the live system), though it doesn't explicitly name the alternative.

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?

The description implies usage context ('backup or migration') which signals when to use this tool — when you need to persist or transport configs. However, it doesn't explicitly state when NOT to use it or contrast with import_connections/connect_from_config, leaving the agent to infer the distinction.

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