mcp-server-rabbitmq

Overview Schema Source Related Servers Discussions Admin

rabbitmq_list_queues

List all queues in a RabbitMQ instance with backlog, unacknowledged message, and consumer metrics to diagnose backlogs and monitor broker health.

Instructions

查询指定实例的全部队列及其积压消息、未确认数与消费者全景指标.

@param connection 目标连接别名，默认为 'default' @param vhost 可选的虚拟主机过滤 @return 队列列表报告或降级提示

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": "rabbitmq_list_queues"
  }
}

Input Schema

Name	Required	Description	Default
`vhost`	No
`connection`	No		default

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Oct 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds useful detail about the returned metrics and the possibility of a 'degraded hint' response, but it does not disclose permissions, read-only nature, rate limits, or pagination behavior.

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 compact and front-loads the core purpose before the parameter annotations. Every line earns its place, though the @param/@return block is slightly repetitive of schema defaults.

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 exists, so return values need not be fully explained, and the description covers both parameters. However, it falls short on sibling differentiation and behavioral safety details, which matter for an agent choosing between this and rabbitmq_get_queue.

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?

Schema description coverage is 0%, but the description compensates by documenting both parameters: the connection alias with its default, and the optional vhost filter. It adds meaning beyond the bare schema, though it does not explain parameter formats or edge cases.

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 first sentence names a specific verb (查询/list), the resource (全部队列/all queues), and the returned metrics (积压消息、未确认数、消费者全景指标). It is clear what the tool does, but it does not explicitly distinguish itself from the sibling rabbitmq_get_queue, which is also queue-focused.

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 that this tool is for listing queues, but it gives no explicit when-to-use guidance, no exclusions, and no mention of the sibling rabbitmq_get_queue or other alternatives. An agent must infer the context entirely.

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