loopsense
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token for CI polling |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| watch_ciB | Watch a GitHub Actions workflow run and emit events on status changes |
| watch_processA | Spawn and monitor a local process, capturing stdout/stderr and exit code |
| watch_fileC | Watch a file or directory for changes using chokidar |
| watch_urlB | Poll an HTTP endpoint and emit events when status or body changes |
| watch_webhookC | Start an HTTP server to receive incoming webhooks |
| check_consequencesB | Get events associated with an agent action, or all recent events |
| list_watchesB | List all active watchers |
| cancel_watchC | Stop and remove a watcher |
| poll_eventsA | Get new events since a timestamp (push notification fallback) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Watches | All currently active watchers |
| Recent Timeline | Last 100 events across all watches |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: cancel_watch, list_watches, and poll_events manage watchers generically, while watch_ci, watch_file, watch_process, watch_url, and watch_webhook each target a specific resource type (GitHub Actions, files, processes, URLs, webhooks). check_consequences stands alone for event retrieval. No ambiguity exists between tools.
All tools follow a consistent verb_noun pattern with snake_case: cancel_watch, check_consequences, list_watches, poll_events, watch_ci, watch_file, watch_process, watch_url, watch_webhook. The naming is predictable and readable throughout the set.
With 9 tools, the count is well-scoped for a monitoring/event-driven server. Each tool earns its place by covering distinct aspects of watching, managing watchers, and retrieving events, without being overly sparse or bloated.
The tool set provides comprehensive coverage for monitoring and event handling: it includes creation (watch_* tools), management (cancel_watch, list_watches), and event retrieval (check_consequences, poll_events). A minor gap is the lack of an update_watch tool for modifying existing watchers, but agents can work around this by canceling and recreating.