Tiny Chat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_CONFIG | Yes | Path to the database configuration JSON file (e.g., /path/to/tiny_chat/database_config.json) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-defaultD | default Information Collection Store |
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 1 tool
With only one tool, there is no possibility of selecting between overlapping tools. The vague description does not create disambiguation issues.
With a single tool, there is no pattern to evaluate for consistency. The name 'search-default' is unconventional but does not conflict with other naming styles.
A single tool for a chat-focused server is clearly insufficient. The tool 'search-default' appears trivial and not aligned with the server's apparent domain.
The server provides no chat-related operations such as messaging or channel management. It appears severely incomplete for a chat server, offering only a vague search capability.