session-watcher
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_watcherA | Start (or reuse) the Session Watcher dashboard server; returns its URL. Never returns metric values. |
| stop_watcherB | Stop the managed Session Watcher server. |
| watcher_statusA | Report whether the Session Watcher server is running and its URL. |
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 3 tools
Each tool has a distinct purpose: starting, stopping, or checking status of the watcher server. No overlap or ambiguity.
All names use snake_case and follow a verb_noun or noun_noun pattern consistently, though 'watcher_status' is a noun phrase while the others are imperative verbs.
Three tools is within the typical 3-15 range and perfectly scoped for the server's purpose of managing a session watcher dashboard.
The tool set covers the full lifecycle of the watcher server: start, stop, and status check. No obvious gaps for the stated purpose.