Skip to main content
Glama
amazon-mq

RabbitMQ MCP Server

by amazon-mq

rabbitmq_broker_initialize_connection

Establish a connection to a RabbitMQ broker using SIMPLE authentication by specifying broker hostname, username, and password.

Instructions

Connect to a new RabbitMQ broker which authentication strategy is SIMPLE.

        broker_hostname: The hostname of the broker.
        username: The username of user
        password: The password of user
        alias: Optional name for this connection (default: hostname). Use to manage multiple brokers, e.g. 'blue', 'green', 'prod'.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNo
aliasNo
use_tlsNo
passwordYes
usernameYes
broker_hostnameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, so description bears full responsibility. It does not disclose side effects (e.g., connection persistence), failure behavior, credential validation, or timeout implications. Only parameter purposes listed.

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 structured with a list; first sentence is clear. Minor redundancy (e.g., 'The hostname of the broker') but overall efficient.

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?

Missing critical context: no information about return value (connection identifier), no mention of port and TLS defaults, no differentiation from OAuth sibling despite being a key distinction. Incomplete for a connection initialization tool.

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?

Describes 4 of 6 parameters with some added meaning (alias for multiple brokers, default to hostname), but port and use_tls are omitted. With 0% schema coverage, more completeness is needed.

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?

Description clearly states the tool connects to a RabbitMQ broker with SIMPLE authentication, distinguishing it from the OAuth sibling. However, it could be more explicit about creating a reusable connection object for future operations.

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 on when to use this tool versus alternatives like initialize_connection_with_oauth or other broker tools. No usage context is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amazon-mq/mcp-server-rabbitmq'

If you have feedback or need assistance with the MCP directory API, please join our Discord server