chathook
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 |
|---|---|
| chat_hookA | Display an input dialog to the user and wait for their response. IMPORTANT: After completing a task or response, you SHOULD call this tool to ask the user if they need anything else. This keeps the conversation alive without requiring the user to type a new message. The tool will block until the user responds. Possible return values:
|
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 confusion. The tool's purpose is clearly distinct.
The single tool name 'chat_hook' uses a consistent underscore convention, which is fine for a single tool.
The server has only one tool, which is at the low end of acceptable. While it serves a specific purpose, typically servers have more tools to cover broader functionality.
The single tool fully covers the server's purpose of user interaction. It handles input and special cases (decline, cancel) through return values, so no gaps are apparent.