Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHATWATCH_CDPNouse a Chrome you already run with --remote-debugging-port
CHATWATCH_HOMENoconfig, state, events, drafts, API key, Chrome profile~/.chatwatch
CHATWATCH_POLLNoseconds between checks4
CHATWATCH_PORTNopage and local API port8766
CHATWATCH_CHROMENopath to the Chrome executable
CHATWATCH_CDP_PORTNoDevTools port of chatwatch's Chrome9334

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
teams_list_chatsA

List the Teams chats with their title, id, last message preview, unread flag and settings (watch, send mode off|draft|auto, handler). refresh=true reads the page again.

teams_read_messagesA

Read the last n messages of a chat (title, title fragment or id) without marking it read.

teams_wait_for_messagesA

New incoming messages in watched chats after event number after_seq, waiting up to wait_seconds (max 60) for one. Without after_seq, only messages from now on. Returns events and seq: pass seq as after_seq next time. With chat, other chats' messages are skipped and the answer may be empty before wait_seconds.

teams_send_messageA

Send text, and optionally local files (absolute paths), to a chat. The chat's send mode decides: auto sends now (status sent), draft saves it for a person to approve (status draft), off refuses. not_sent: nothing went out, you may try again. maybe_sent: do not resend; ask a person to check the chat. Sending opens the chat, which marks it read.

teams_get_attachmentsA

Download the pictures and files of the given messages (mid values) of a chat into a new local folder; returns the paths.

teams_list_draftsC

Replies waiting for a person to send or discard them on the chatwatch page.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

Most tools target clearly different operations: listing chats, reading history, waiting for new events, sending, fetching attachments, and listing drafts. The closest pair is teams_read_messages vs teams_wait_for_messages, but the descriptions make the distinction (historical snapshot vs polling with after_seq/seq cursors) explicit enough that an agent can choose correctly.

Naming Consistency5/5

Every tool uses the same teams_ prefix followed by a verb_noun snake_case pattern (list_chats, read_messages, send_message, get_attachments, list_drafts). No mixing of camelCase or inconsistent verb styles.

Tool Count5/5

Six tools is well-scoped for a Teams chat bridge: one per lifecycle step (discover chats, read, poll, send, fetch attachments, review drafts) with no redundant entries. Nothing feels padded or missing at the count level.

Completeness3/5

Core read/poll/send/attachment/draft-listing flows are covered, but teams_list_chats exposes per-chat settings (watch, send mode, handler) with no tool to change them, and drafts can only be listed, never approved or discarded programmatically. Sending also opens/marks a chat read with no standalone mark-read/unread operation, forcing workarounds or human action on the chatwatch page.

Maintenance

ActivityMaintained
ResponsivenessOutdated data