Skip to main content
Glama
sansong089
by sansong089

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RABBITMQ_HOSTNoRabbitMQ management hostlocalhost
RABBITMQ_PASSNoRabbitMQ passwordguest
RABBITMQ_PORTNoRabbitMQ management port15672
RABBITMQ_USERNoRabbitMQ usernameguest
RABBITMQ_VHOSTNoRabbitMQ virtual host/

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_cluster_statusC

获取RabbitMQ集群状态

list_queuesC

列出指定虚拟主机下的所有队列

create_queueC

创建队列

delete_queueD

删除队列

list_exchangesC

列出指定虚拟主机下的所有交换机

create_exchangeD

创建交换机

get_exchangeC

获取交换机信息

delete_exchangeC

删除交换机

list_bindingsB

列出指定虚拟主机下的所有绑定

create_bindingC

创建交换机到队列的绑定

delete_bindingC

删除交换机到队列的绑定

list_vhostsC

列出所有虚拟主机

create_vhostC

创建虚拟主机

delete_vhostC

删除虚拟主机

list_usersB

列出所有用户

create_userC

创建用户

delete_userC

删除用户

list_connectionsB

列出所有连接

publish_messageC

向交换机发布消息

consume_messageC

从队列消费一条消息 (消息将被删除)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct resource and action (e.g., list_vhosts vs. create_vhost vs. delete_vhost, publish_message vs. consume_message). There is no meaningful overlap; an agent can reliably select the intended operation.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (list_*, create_*, delete_*, get_*, publish_*, consume_*). The convention is predictable throughout, with no mixing of styles or vague verbs.

Tool Count4/5

20 tools is slightly above the typical 3–15 sweet spot, but the set covers distinct RabbitMQ resources without obvious redundancy. The count is reasonable for a management server spanning vhosts, users, queues, exchanges, bindings, and messages.

Completeness3/5

Core create/list/delete operations exist for vhosts, users, queues, exchanges, and bindings, and exchange has a get operation, but many resources lack detailed get or update tools (users, queues, vhosts, bindings). Additional gaps include queue purge, message ack/reject, and connection management, though agents can partially work around these via list operations.

Maintenance

ActivityInactive
ResponsivenessNo issues