Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEBUGNoEnable detailed logging for development and troubleshootingfalse
CONTENT_FILTERING_ENABLEDNoEnable/disable filtering of personal conversations (sports, politics, entertainment) to keep summaries focused on worktrue

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

NameDescription
generate_daily_summaryB

Generate a concise daily productivity summary from today's Slack, Calendar, and Gmail activity. Perfect for end-of-day wrap-ups and next-day planning.

generate_weekly_summaryC

Generate a comprehensive weekly productivity summary from Slack, Calendar, and Gmail data. Returns structured summary with optional HTML/Markdown output.

list_summariesC

List previously generated weekly summaries from the summaries directory.

get_summaryC

Retrieve a specific weekly summary by filename or date range.

get_quick_statsB

Get quick productivity metrics (Slack, Calendar, Gmail) without generating a full summary. Fast lightweight query.

compare_periodsC

Compare productivity statistics between two time periods. Generates comparison reports in HTML and Markdown formats showing trends and changes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct purposes, with clear separation between daily vs. weekly summaries, quick stats vs. full summaries, and retrieval vs. generation. However, 'generate_weekly_summary' and 'get_summary' could cause some confusion since both relate to weekly summaries, though one generates new data while the other retrieves existing ones.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with clear, descriptive verbs (compare, generate, get, list) and nouns (periods, daily_summary, weekly_summary, quick_stats, summary, summaries). There are no deviations in style or convention throughout the set.

Tool Count5/5

Six tools is well-scoped for a productivity summary server, covering generation (daily, weekly, comparison), retrieval (list, get), and quick queries without being overwhelming. Each tool appears to serve a specific, necessary function in the workflow.

Completeness4/5

The tool set covers core productivity summary operations well, including generation, comparison, and retrieval. A minor gap is the lack of update or delete tools for managing existing summaries, which might limit agent flexibility, but the core workflows for creating and accessing summaries are adequately supported.