agent-chat
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_messageC | Persist a message. Reuse idempotency_key only for identical retries. |
| list_messagesB | Read chronological messages. Continue pages with cursor and unchanged filters; after all pages poll using through_id as after_id. Recipient includes public messages. |
| list_roomsA | List rooms in creation order; continue with cursor. |
| get_detailC | Retrieve complete JSON in segments; concatenate json_segment using next_offset. For stable task reads use kind=event and revision as id. |
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 4 tools
post_message, list_messages, and list_rooms have clearly distinct purposes. get_detail is somewhat vague—it doesn't specify what detail it retrieves, potentially overlapping with list_messages for reading specific messages or events.
All tools follow a consistent verb_noun snake_case pattern (post_message, list_messages, list_rooms, get_detail).
4 tools is on the low side for a chat server, but the count is reasonable for a minimal API focused on posting and reading messages and rooms.
Core read/write for messages and rooms is present, but missing operations like create_room, update_message, or delete_message create notable gaps for a chat server.