Agent-MQ
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mq_addC | Add an agent to the message queue |
| mq_sendC | Send a message to a target agent by name |
| mq_recvC | Receive and consume messages for an agent. Poll periodically to check for new messages. |
| mq_lsB | List all registered agents |
| mq_historyC | View delivered message history |
| mq_loginC | Login with a token. Server defaults to config. |
| mq_logoutC | Disconnect from server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity: mq_add adds agents, mq_history views history, mq_login handles authentication, mq_logout disconnects, mq_ls lists agents, mq_recv consumes messages, and mq_send sends messages. The actions and targets are well-defined and non-overlapping.
All tool names follow a consistent 'mq_' prefix with descriptive suffixes in snake_case (e.g., mq_add, mq_history, mq_login). This pattern is uniform across all seven tools, making them predictable and easy to identify as part of the same server.
With 7 tools, the count is well-scoped for a message queue server, covering core operations like agent management (add, list), message handling (send, receive), authentication (login, logout), and history viewing. Each tool earns its place without redundancy or bloat.
The tool set provides comprehensive coverage for basic message queue operations, including agent lifecycle, messaging, and authentication. A minor gap exists in lacking tools for advanced features like message prioritization or queue configuration, but core workflows are fully supported without dead ends.