IDE Chat Summarizer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAT_NOTES_DIR | No | Custom directory path for storing chat summaries | ~/Documents/ChatSummaries |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| summarize_chatA | Summarize chat history and save it as a markdown file. Args: chat_history: The chat conversation text to summarize title: Optional title for the summary (will be used in filename) summary_style: Style of summary - 'brief', 'detailed', or 'bullet_points' include_full_history: Whether to include the full chat history in the summary file (default: True) create_separate_full_history: Whether to create a separate file with just the full history (default: False) Returns: Path to the created summary file and preview of the summary |
| summarize_large_chatB | Handle extremely large chat histories by chunking them into manageable pieces. Each chunk gets its own summary, then creates a master summary. Args: chat_history: The large chat conversation text to summarize title: Optional title for the summary chunk_size: Size of each chunk in characters (default: 50,000) overlap: Overlap between chunks in characters (default: 5,000) Returns: Information about the chunked summaries created |
| list_summariesB | List recent chat summaries from the notes directory. Args: limit: Maximum number of summaries to list (default: 10) Returns: List of recent summary files with their creation dates |
| delete_summaryB | Delete a chat summary file. Args: filename: Name of the summary file to delete Returns: Confirmation message |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_summary_prompt | Generate a prompt for creating chat summaries. Args: conversation_type: Type of conversation (general, technical, meeting, brainstorm) focus_area: What to focus on (all, decisions, action_items, insights) Returns: A customized prompt for summarizing the conversation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_notes_directory_info | Get information about the notes directory |
TDQS
Scored across 4 tools
The tools are mostly distinct with clear purposes: list, create (summarize), and delete. However, summarize_chat and summarize_large_chat have overlapping functionality for summarizing chats, which could cause confusion about when to use each. The descriptions help differentiate them based on chat size, but the overlap is notable.
All tool names follow a consistent verb_noun pattern (e.g., delete_summary, list_summaries, summarize_chat, summarize_large_chat). The naming is predictable and readable, with no deviations in style or convention.
With 4 tools, the count is reasonable for a chat summarizer server, covering core operations like list, create, and delete. It's slightly lean but well-scoped, though adding a tool for updating or viewing summaries might enhance completeness.
The toolset covers create (summarize), list, and delete operations, but lacks a tool for updating or retrieving a specific summary (e.g., get_summary). This gap could hinder agents from modifying existing summaries or accessing details without listing all. The domain is chat summarization, and while basic workflows are supported, the absence of update/retrieve is a notable omission.